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

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

Now I'm a pretty lazy person and am prepared to work quite hard in order to avoid work.

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

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

Comprehensiveness is the enemy of comprehensibility.

So I hope I’ve made clear that imposing agile methods is a very red flag.