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

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.

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

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

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

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

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