It's better to wait for a productive programmer to become available than it is to wait for the first available programmer to become productive.

It's better to wait for a productive programmer to become available than it is to wait for the first available programmer to become productive.

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.

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

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.

The primary purpose of software estimation is not to predict a project's outcome; it is to determine whether a project's targets are realistic enough to allow the project to be controlled to meet them.