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

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

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

Comprehensiveness is the enemy of comprehensibility.

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

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

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