Never in the annals of software engineering was so much owed by so many to so few lines of code

I can only think of so many good ideas in a week. Having other people contribute makes my life easier.

A pattern is an idea that has been useful in one practical context and will probably be useful in others.

Comprehensiveness is the enemy of comprehensibility.

When you actually sit down to write some code, you learn things that you didn't get from thinking about them in modeling terms...there is a feedback process there that you can only really get at from executing some things and seeing what works

When to use iterative development? You should use iterative development only on projects that you want to succeed.

Comparing to another activity is useful if it helps you formulate questions, it's dangerous when you use it to justify answers.