Inside every well-written large program is a well-written small program.
When debugging, novices insert corrective code; experts remove defective code.
Each new user of a new system uncovers a new class of bugs.
The most exciting phrase to hear in science, the one that heralds new discoveries, is not 'Eureka!', but 'That's funny...'
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.
With good program architecture debugging is a breeze, because bugs will be where they should be.
If debugging is the process of removing bugs. Then programming must be the process of putting them in.
Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code.
Another effective technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed “Never mind, I see what's wrong. Sorry to bother you.” This works remarkably well; you can even use non-programmers as listeners. One university computer center kept a teddy bear near the help desk. Students with mysterious bugs were required to explain them to the bear before they could speak to a human counselor.
At the source of every error which is blamed on the computer you will find at least two human errors, including the error of blaming it on the computer.
Code smells.
Anything that can possibly go wrong, will go wrong.
