A typical software project can present more opportunities to learn from mistakes than some people get in a lifetime.

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.

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.

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.

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

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.