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.

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.

In my experience, you either have encapsulation and abstraction or you have neither. There is no middle ground.

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.

Good visual layout shows the logical structure of a program.

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