The Pragmatic Programmer (1999)
The Pragmatic Programmer is a 1999 computer programming book written by Andy Hunt and David Thomas.
Andy Hunt and Dave Thomas wrote this in 1999 for working developers, and it reads like advice from two senior engineers who have seen every way a project can rot. It covers the daily craft of software: writing code that is easy to change, automating the boring parts, testing honestly, and taking responsibility for what you ship. The lessons come as short, named principles with real examples rather than abstract theory. Later updated editions keep the material current, but the core stays about attitude and habits more than any single language.
Quick answers
What is The Pragmatic Programmer about?
Andy Hunt and Dave Thomas wrote this in 1999 for working developers, and it reads like advice from two senior engineers who have seen every way a project can rot. It covers the daily craft of software: writing code that is easy to change, automating the boring parts, testing honestly, and taking responsibility for what you ship. The lessons come as short, named principles with real examples rather than abstract theory. Later updated editions keep the material current, but the core stays about attitude and habits more than any single language.
When was The Pragmatic Programmer published?
The Pragmatic Programmer was published in 1999.
Who made The Pragmatic Programmer?
The Pragmatic Programmer was written by Andy Hunt, David Thomas and Dave Thomas.
Official site
Similar books
A few thoughts on The Pragmatic Programmer
Keep it on the desk, not the shelf. The chapters work as standalone reminders you can reread between projects, and the advice ages well because it targets how you think rather than which framework is trendy this year. Good for a first job and still useful a decade in.
More books to sharpen your software craft
The Pragmatic Programmer teaches software as a daily craft, short named principles drawn from real projects rather than theory. These programming books sit on the same shelf, focused on how working developers actually build, structure, and reason about code, from data structures to compilers to the discipline of writing something you can change later.