3 ms·
The debugging process you described has the same drawback as editing your own essay: you see what you think you wrote, not necessary what is there. That is, you
by scott_s 16y ago
The debugging process you described has the same drawback as editing your own essay: you see what you think you wrote, not necessary what is there. That is, you know what a certain chunk of code is supposed to do, so you might glance over it and not actually read it again.
Experienced programmers know this, and constantly re-read their code to make sure it does what they think it does. But I just finished teaching programming to complete beginners, and this was a big hurdle. They would constantly say "My code's right, but the answer is wrong," not realizing the absurdity of the statement. It took a lot of time and patience to train them to always read the code they wrote.
- JoeAltmaier 16y agoAgreed. I am "reading" my code, a page/method/block at a time, but not with an internal dialog. And I'm certainly not "arguing with myself" in words about what it does. So the thinking is occurring below/behind/between the words.