by David Thomas
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.
In this collection, The Pragmatic Programmer references 2 other books and is cited by 10 other books.
It draws on Refactoring and The Design of Everyday Things.
It’s picked up by Deep Work, Clean Code and Refactoring and 7 others.
Scroll down to read the exact passages where other authors reference this book and what they say about it.
The Pragmatic Programmer is the book that software engineers across specialties name as formative to their craft, and its principles ripple through the most influential programming texts of the last two decades. Robert C. Martin credits it in Clean Code, Martin Fowler references it in both Refactoring and Patterns of Enterprise Application Architecture, and Eric Evans cites its emphasis on expressive code and orthogonality as prerequisites for domain-driven design.
Cal Newport uses it in Deep Work as proof that knowledge workers should treat cognitive skills with the same rigor software engineers bring to code, and Will Larson references it as essential for staff-engineer-level craftsmanship. Readers praise its timeless, language-agnostic advice -- DRY, orthogonality, and the craftsman's mindset it advocates have become so fundamental that many developers absorb them without realizing the source.
The books Thomas references and why each one mattered to the argument.
Hunt and Thomas reference Fowler's Refactoring.
Pragmatic Programmer references Norman's design principles.
The exact passages where other authors bring up “The Pragmatic Programmer” and what they take from it.
Newport references The Pragmatic Programmer's philosophy of craftsmanship, using it to argue that knowledge workers should treat their cognitive skills with the same rigour as software engineers treat their code.
Martin references The Pragmatic Programmer for craftsmanship.
Fowler references Pragmatic Programmer on continuous improvement.
Humble references Pragmatic Programmer on automation.
Larson references The Pragmatic Programmer for staff engineer craftsmanship.
Evans's bibliography cites Hunt and Thomas's Pragmatic Programmer for its emphasis on expressive code and orthogonality - prerequisites for the ubiquitous language to appear in the codebase itself.
How ideas flow through the citation network. Ancestors are books this title builds on; descendants are books that build on it.
Directly cites
Directly cited by
Books from completely different categories that share citation overlap with this one. These are the reads you would not find by browsing a single shelf.
The Personal MBA
Josh Kaufman
High Output Management
Andrew Grove
Universal Principles of Design: 125 Ways to Enhance Usability, Influence Perception, Increase Appeal, Make Better Design Decisions, and Teach through Design
William Lidwell, Kritina Holden, Jill Butler
100 Things Every Designer Needs to Know About People
Susan Weinschenk
Emotional Design: Why We Love (or Hate) Everyday Things
Don Norman
Change by Design: How Design Thinking Transforms Organizations and Inspires Innovation
Tim Brown
Books with the highest citation overlap within the same categories.
This book and its direct connections. Hover a node to see its title, click to visit.
Hover a node to highlight its connections. Click to open the book page. Node size reflects total citation links.
