Even when you have skilled, motivated, hard-working people, the wrong team structure can undercut their efforts instead of catapulting them to success. A poor team structure can increase development time, reduce quality, damage morale, increase turnover, and ultimately lead to project cancellation.

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.

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.

Good code is its own best documentation.

Engineering is the application of scientific principles toward practical ends. If the engineering isn't practical, it's bad engineering.

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

Good visual layout shows the logical structure of a program.