It's hard enough to find an error in your code when you're looking for it; it's even harder when you've assumed your code is error-free.

Software projects fail for one of two general reasons: the project team lacks the knowledge to conduct a software project successfully, or the project team lacks the resolve to conduct a project effectively.

In software, the chain isn't as strong as its weakest link; it's as weak as all the weak links multiplied together.

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.

Good visual layout shows the logical structure of a program.

It's hard enough to find an error in your code when you're looking for it; it's even harder when you've assumed your code is error-free.

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