|
Was that a Ford Focus I saw in the middle of the pack? 
Along with Antimatter and Dark Matter they've discovered the existence of Doesn't Matter which appears to have no effect on the universe whatsoever!
Rich Tennant 5th Wave
|
|
|
|
|
That's the worst thing I have ever heard.
CPallini wrote: You cannot argue with agile people so just take the extreme approach and shoot him.
:Smile:
|
|
|
|
|
Yeah, its the old KERS back, with more power stored. Its a good idea, really good, storing KE in batteries for later use is going to transform the urban cycle economy of every day cars.
|
|
|
|
|
|
I was walking the dog this morning I saw a suspicious looking man dressed in dark clothing, crossing the street with a ladder. He had even gone to the trouble of disabling the street light so as not to be seen. I got a good look at him though as he was lit up by an oncoming car. I have passed his description on to the Police.
|
|
|
|
|
Blue Waffle wrote: crossing the street with a ladder.
How did he do that?
|
|
|
|
|
|
|
I'm not an expert coder on the level of a lot of the guys here, but I do some at work. What I'm finding is that I like debugging more than the actual coding. Anybody else feel that way?
|
|
|
|
|
Kind of. Churning out the code can get boring and repetitive. Chasing down bugs gets adversarial and is more of a challenge, more of a thrill when you nail the little buggers.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
Nope, I prefer coding.
If I have to debug it means my code is not good and I have to work better next time.
I'd rather be phishing!
|
|
|
|
|
I'm with you on that one!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
I prefer the coding. Debugging is useful, but Bob help me when i am debugging code written so good that he belongs in The Weird & The Wonderful section... in a wooden box.
Microsoft ... the only place where VARIANT_TRUE != true
|
|
|
|
|
Yes. Most of my professional life was in tech support so I was trying to debug other people's code. I did enjoy the occasional break to write some code for myself, but soon got fed up and went back to debugging.
|
|
|
|
|
Certainly not.
Nothing beats the feeling from nailing your code at first try.
And before anyone start the sarcastic commenting, I mean strictly from a programming point of view.
|
|
|
|
|
I've only experienced that once and have to agree with you. Maybe if I experienced it more often I would have been more in the forefront of my thoughts.
|
|
|
|
|
It's not like it happens a lot to me either, (hardly at all to be honest) that's why it feels so good when it actually does.
|
|
|
|
|
I think they go both hand in hand.
you need to learn from bugs to write better code and you can't really understand what the code does until it breaks that what I believe.
But I in the mundane day of just bashing out code I prefer to chase bugs as chriselst said it can be quite satisfying to get the little bleeder.
But I also enjoy the coding of something new and different more than trying to debug it.
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
I have to agree. I learn a lot from chasing down the answers to the bugs to get the program to act how I want it to. Especially since a lot of times I'm parsing text files. I think I've learned a 100 different ways to manage strings.
|
|
|
|
|
Given that right now I'm trying to figure out why the application reports one record when the database query says I should have some 70 or so records, well, this isn't fun. It's not code that I've written, if I had I would have done it a lot differently (yes, I know, the mantra of all programmers working on someone else's stuff), but I definitely prefer writing code than debugging.
That said, I like to write code as if I'm debugging -- what I mean by that is that I imagine the whole stack, the possible exceptions, the possible paths the code can take, and I try coding for all of that. I imagine everyone does that. And when working with F#, I write everything first in the interactive console, test it, then put it into the application. I would love for something like FSI for C# development.
But personally, my first and true love is architecture. But I would have to say that many of my beautiful architecture ideas turn into puddles of mud when I actually try coding them against real world requirements. A good way to learn the difference between theory and application!
Marc
|
|
|
|
|
Marc Clifton wrote: That said, I like to write code as if I'm debugging -- what I mean by that is that I imagine the whole stack, the possible exceptions, the possible paths the code can take, and I try coding for all of that.
I try to do that to. But sometimes it comes down to not getting the output I need from a certain block of code.
|
|
|
|
|
Marc Clifton wrote: I would love for something like FSI for C# development.
After working in C++ for a very long time, with edit-compile-debug cycle lengths measured in minutes or even hours, I find the 15-45 second turnaround time from my C# development refreshingly quick. On top of that, I have my entire C# application in a single solution. My C++ stuff had to be broken up into several solutions to bring the individual compile times down to something reasonable.
In other words, there is a perspective here  .
Software Zen: delete this;
|
|
|
|
|
well actually both are like two side of a coin we can't say exactly that i like this one more than that. good code helps in reducing the chance of generating bug and good debugging skill helps to write better code. as a Programmer i like both coding and debugging.
Ravi Khoda
|
|
|
|
|
I don't have bugs in my code, just undocumented features.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
I'm definitely a coder. Debugging means either (i) you didn't write your code well enough in the first place, so you have to debug it later, which is a failure and I don't like failing; or (ii) you are working in someone else's code which is always painful, and if you're debugging it it means it doesn't work and isn't well enough documented or tested to isolate the problem without debugging. Neither of those things is fun to me.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
