The Pragmatic Programmer - Wikipedia

Open original

A 1999 book by Andrew Hunt and David Thomas offering practical tips on software development rather than a formal theory. It introduced or popularized ideas like DRY and rubber duck debugging, and a 2019 20th-anniversary edition updated it for modern tools and practices.

  • The book is a collection of pragmatic tips, not a systematic theory, built around analogies and short stories like broken windows, stone soup, and the boiling frog.
  • It describes a pragmatic programmer through traits such as early adoption, fast adaptation, inquisitiveness, critical thinking, realism, and being a jack-of-all-trades.
  • It coined or popularized DRY (don't repeat yourself) and rubber duck debugging, and it is still used as a university textbook.

*The Pragmatic Programmer* was written by Andrew Hunt and David Thomas and published by Addison-Wesley in October 1999, with 320 pages. It became a textbook in some university courses and was the first title under the Pragmatic Bookshelf label. A 20th anniversary second edition, *Your Journey to Mastery*, came out in 2019, with major revisions to reflect two decades of change in tools and practice. The book is not a systematic theory of software engineering. It is a collection of practical tips aimed at improving how developers work. The authors describe a pragmatic programmer as someone who adopts useful technology early, adapts quickly, stays curious and thinks critically, keeps a realistic view of what can be done, and is a jack-of-all-trades. Much of the teaching happens through analogies and short stories, such as the broken windows theory (small neglected problems breed bigger ones), stone soup (getting people to contribute by starting with something small), and the boiling frog (gradual decline that goes unnoticed). Two ideas from the book have spread well beyond it. DRY, "don't repeat yourself," is a principle the authors named or popularized, and it is now standard vocabulary in code reviews. Rubber duck debugging, where you explain your code line by line to an inanimate object until the bug surfaces, comes from a story in the book and is probably the most widely known piece of its advice. The citations on the page point to the book being recommended in lists of influential programming reading, though those lists are informal rather than authoritative.

Ask about this article