![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
"Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?" -- Brian W. Kernighan
[Also quoted as: "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."]
*Swats bug*
My own experience is that the prime attributes for debugging are persistence, systematic work habits, and good documentation. I'm not trying to be clever; I'm trying to spot the place in the code where I tried to be *too* clever.
Or, alternatively, find the comma that had been supposed to be a period. That's been my most frustrating debugging to date; it took me 3 weeks of poring over a mere 300 lines of code to spot the goof. When I finally found it, I had stared straight at it, what? a hundred times? Two? More?
*hugs*,
Joel
Re: *Swats bug*