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.

... 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.

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

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.

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.

Good visual layout shows the logical structure of a program.