Don't document bad code - rewrite 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

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.

Do what you think is interesting, do something that you think is fun and worthwhile, because otherwise you won't do it well anyway.

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

Some compilers allow a check during execution that subscripts do not exceed array dimensions. This is a help, but not sufficient. First, many programmers do not use such compilers because They're not efficient. (Presumably, this means that it is vital to get the wrong answers quickly.)

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