Design work doesn't just satisfy requirements, it elicits them.

Men and months are interchangeable commodities only when a task can be partitioned among many workers with no communication among them.

You can learn more from failure than success. In failure you're forced to find out what part did not work. But in success you can believe everything you did was great, when in fact some parts may not have worked at all. Failure forces you to face reality.

Adding manpower to a late software project makes it later

Systematically identity top designers as early as possible. The best are often not the most experienced.

Adjusting to the requirement for perfection is, I think, the most difficult part of learning to program.

I have never seen an experienced programmer who routinely made detailed flow charts before beginning to write programs.