Martin Fowler

Martin Fowler

Software Engineer, Author

Martin Fowler is a British software developer, author, and chief scientist at ThoughtWorks, specialising in object oriented design, refactoring, and enterprise software architecture. His influential book Refactoring: Improving the Design of Existing Code established systematic approaches to restructuring code that are now standard practice across the software industry. His work on Patterns of Enterprise Application Architecture provided foundational design patterns for building scalable business systems.

2
Books Written
3
Books Recommended

Books by Martin Fowler

Refactoring by Martin Fowler

Refactoring

by Martin Fowler

star4.4

Fowler argues that improving code structure without changing behaviour is essential to software longevity. Small, disciplined refactoring steps reduce complexity and prevent technical debt from compounding.

technology
Patterns of Enterprise Application Architecture by Martin Fowler

Patterns of Enterprise Application Architecture

by Martin Fowler

star4.2

Fowler catalogs over forty patterns for the recurring problems of enterprise software, layering, domain logic organisation, object-relational mapping, web presentation, and concurrency, distilling the architectures he observed across hundreds of Java and .NET projects. Patterns like Active Record, Data Mapper, Unit of Work, and Repository became the standard vocabulary for backend architecture.

technologysoftware engineering

Most Recommended by Martin

The books Martin Fowler references, cites, and recommends most frequently.

The Pragmatic Programmer by David Thomas

The Pragmatic Programmer

by David Thomas

star4.4

Thomas and Hunt argue that great software comes from a craftsman's mindset: think critically, take ownership, and never stop learning. Pragmatic techniques like DRY and orthogonality compound into mastery.

technology
The Mythical Man-Month by Frederick Brooks

The Mythical Man-Month

by Frederick Brooks

star4

Brooks argues that adding more programmers to a late project makes it later - a principle now known as Brooks' Law. The deeper insight: software complexity grows faster than headcount, making communication the real bottleneck.

technologybusiness
Clean Code by Robert C. Martin

Clean Code

by Robert C. Martin

star4.3

Martin argues that code is read far more often than written. Clean code, with clear names, small functions, and minimal dependencies, is a professional responsibility, not a luxury.

technology

Influence Map

Who Martin draws from, and who draws from Martin — aggregated across every book in this collection. Counts show the number of citation links, not the depth of each one.

Martin cites most often

  1. 2 links
  2. 2 links
  3. 1 link

Authors who cite Martin most often

  1. 1 link
  2. 1 link
  3. 1 link
  4. 1 link
  5. 1 link
  6. 1 link
  7. 1 link