One of the big dangers is to pretend that you can follow a predictable process when you can't.

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

Why is composing symphonies tough? I don't know. It's just very few people in the world can do it well. And I think that's the case with upfront design. It is very hard to do well.

The biggest issue on software teams is making sure everyone understands what everyone else is doing.

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

I can't choose whether someone is offended by my actions. I can choose whether I care.

One of the things I've been trying to do is look for simpler or rules underpinning good or bad design. I think one of the most valuable rules is avoid duplication. "Once and only once" is the Extreme Programming phrase.