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

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

In almost all cases, I’m opposed to setting aside time for refactoring. In my view refactoring is not an activity you set aside time to do. Refactoring is something you do all the time in little bursts.

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.

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

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

If you're afraid to change something it is clearly poorly designed.