Mechanical rules are never a substitute for clarity of thought.

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.

Get the weirdnesses into the data where you can manipulate them easily, and the regularity into the code because regular code is a lot easier to work with

Another effective [debugging] 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.

If you're as clever as you can be when you write it, how will you ever debug it?

Trying to outsmart a compiler defeats much of the purpose of using one.

An effective way to test code is to exercise it at its natural boundaries