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

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

Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.

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.

Comparing to another activity is useful if it helps you formulate questions, it's dangerous when you use it to justify answers.

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

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