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.

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

I find that writing unit tests actually increases my programming speed

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

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

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

Any fool can write code that a computer can understand. Good programmers write code that humans can understand.