If cleverness was the relevant value in debugging, this would be true.
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?
*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*