45 Quotes by Martin Fowler

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

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

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.

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.

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.

I’ve learned to always avoid saying “always”

Never in the annals of software engineering was so much owed by so many to so few lines of code.