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.

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

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

I've learned to always avoid saying "always"

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

If you're a technical lead, you need to be coding.

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