Résumé de The Pragmatic Programmer

The Pragmatic Programmer by David Thomas and Andrew Hunt is a foundational text in software engineering, first published in 1999 and updated for its 20th anniversary in 2019. Thomas and Hunt structure the book around dozens of numbered "tips" and memorable heuristics rather than a single methodology, drawing on their experience as consultants who observed how working programmers actually build and maintain systems. Central to the book is the metaphor of the "pragmatic programmer" as a craftsman who takes responsibility for their work, avoids technical debt, and refuses to live with "broken windows" — small signs of neglect that invite further decay in a codebase. The authors introduce concepts like the DRY principle ("Don't Repeat Yourself"), tracer bullets (building a thin end-to-end skeleton before fleshing out features), and the "good-enough software" argument that perfectionism can be as damaging as carelessness. They also emphasize "orthogonality," designing components so that changes in one area don't ripple unpredictably through others. Other recurring ideas include programming by coincidence versus programming deliberately, the importance of estimating and communicating about schedules realistically, and treating debugging as a scientific process rather than guesswork. The authors discuss automating repetitive tasks, using plain text for durability, and the value of prototyping to throw away rather than to keep. A later section addresses practical craftsmanship concerns such as refactoring, testing, and requirements gathering, framing these as ongoing habits rather than project phases. The book is less a coding tutorial than a set of durable principles about professional conduct, design judgment, and continuous learning. Its tips are cross-referenced throughout, reinforcing the authors' argument that pragmatic programming is a way of thinking rather than a fixed toolkit.