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

It's OK to figure out murder mysteries, but you shouldn't need to figure out code. You should be able to read it.

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

A brute force solution that works is better than an elegant solution that doesn't work.

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.

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.

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.