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.

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.

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.

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.

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

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.