6. Write a lot of comments, especially about the purpose of a code chunk.

Time for me to beat my "comments" drum again.

Ideally comments should not explain the purpose of a code block. The purpose should be self-evident. Moving your code out to a well named method/sub can often help greatly with this.

Instead, comments should explain the WHY behind the particular manner in which you achieve your purpose. Any average programmer should be able to read your code and see easily enough what it does. But even a great programmer might have difficult knowning why you did it a certain way. That's where good comments save a lot of head-scratching.

Tony

Tony