A computer program is a message from a man to a machine. The rigidly marshaled syntax and the scrupulous definitions all exist to make intention clear to the dumb engine.

Product procedure...must securely protect the crown jewels, but, equally important, it must eschew building high fences around the garbage cans.

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

Present to inform, not to impress. If you inform, you will impress.

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.

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

The management question, therefore, is not whether to build a pilot system and throw it away. You will do that. Hence plan to throw one away; you will, anyhow.