The default movement on a software project should be in the direction of taking elements of the software away to make it simpler rather than adding elements to make it more complex.

... programming requires more concentration than other activities. It's the reason programmers get upset about 'quick interruptions' - such interruptions are tantamount to asking a juggler to keep three balls in the air and hold your groceries at the same time.

Good visual layout shows the logical structure of a program.

Trying to apply formal methods to all software projects is just as bad as trying to apply code-and-fix development to all projects.

Engineering is the application of scientific principles toward practical ends. If the engineering isn't practical, it's bad engineering.

The default movement on a software project should be in the direction of taking elements of the software away to make it simpler rather than adding elements to make it more complex.

Good code is its own best documentation. As you're about to add a comment, ask yourself, "How can I improve the code so that this comment isn't needed?" Improve the code and then document it to make it even clearer.