What Martin Fowler thinks about simplicity

@martin-fowler · 21 positions · On ppll ↗

Chief scientist at Thoughtworks and author of Refactoring, Patterns of Enterprise Application Architecture and Refactoring: Ruby Edition. His bliki at martinfowler.com has been the reference text on refactoring, testing and architecture for two decades.

Martin Fowler did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

Filter simplicity · Newest first

Topic

All 21design 5software quality 5coding agents 4simplicity 2AI agents 1curiosity 1cybersecurity 1team size 1

Sort

NewestOldest

Only Martin Fowler on simplicity. See everyone on simplicity

2 dated positions, 2003 to 2015, in their own words. Our reading of what Martin Fowler has said — not written or endorsed by them.

2 positions so far — this page is not yet offered to search engines.

1. 3 Jun 2015

   Our readingBuild a new application as a monolith first, even when you are confident it will eventually need microservices.

   Their wordsThis leads to a powerful argument for a monolith-first strategy, where you should build a new application as a monolith initially, even if you think it's likely that it will benefit from a microservices architecture later on.

   ↗MonolithFirstmartinfowler.com 2nd of 3 in this piece

2. 12 years earlier

3. 29 Aug 2003

   Our readingLines of code cannot measure productivity, because better-designed code is shorter.

   Their wordsAny good developer knows that they can code the same stuff with huge variations in lines of code, furthermore code that's well designed and factored will be shorter because it eliminates the duplication.

   ↗CannotMeasureProductivitymartinfowler.com 2nd of 2 in this piece