The Pragmatic Programmer book
A career-spanning collection of engineering principles, organized as discrete tips. The 20th-anniversary edition is the one to read.
A career-spanning collection of engineering principles, organized as discrete tips. The 20th-anniversary edition is the one to read.
why it matters
If you've absorbed the basic mechanics of programming, this is the book that shapes how you think about *practice* — the meta-skills that compound. DRY, orthogonality, tracer bullets, broken windows, crashing early — most of these are now standard vocabulary for craft-conscious engineers. Read once early in your career, again 5-10 years in.
key ideas
- DRY (Don't Repeat Yourself) is about knowledge, not code — duplication of intent is the bug, even when code looks different
- Orthogonality: changes in one part of the system shouldn't ripple to unrelated parts
- Tracer bullets: build a thin slice of the whole system end-to-end before fleshing it out
- Broken windows: small unaddressed problems compound; fix or document them immediately
- Crash early: an early failure is a feature; failing late hides the actual problem
- Tip-based structure makes it skimmable; revisit individual tips as situations come up
memorable framings
- 'Don't live with broken windows.'
- 'Stone soup' as a method for getting buy-in by starting with a small visible thing
who should read it
Read in your first 5 years. Re-read every 5-10 years; different tips become salient at different career stages.