What one book should every programmer read? A recommendation.
Tags: books, programming
Published: 2020-12-03 19:20:44

It seems like every programming blog out there has **A list of 10 books every programmer should read.** The funny thing is, the list is invariably the same 10 books that have been listed for the last decade. 

_The same 10 books._

Are they good books? Yes. They are fantastic. Are they applicable to everybody? Yes, eventually. Do they impart knowledge that will be useful _right now_ no matter where you are in your career? No, not all of them do.

Today, I'm going to buck the trend of regurgitating the same list of books that I'd wager have already been listed dozens if not hundreds of times on this very platform. Instead, I'm going to recommend the one book that, in my opinion, can illuminate your entire journey - whether you're on the first step of that journey, or well along the way.

## **The Pragmatic Programmer**<br> _by Andrew Hunt and  David Thomas_.

Why this book? Why not some book on a programming language, or algorithms, or how to pass an interview, or software architecture, or design patterns, etc, etc, etc? Because this book, this one book, is approachable and applicable for everyone. It provides insights into practical ways that ANYONE can elevate their craft.

**_It is readable._**

Readable? Yes, by even the juniorest of juniors. But, it's also chock full of wisdom that is valuable to the most senior of seniors. I, personally, have read it multiple times and have learned something new in every reading. It teaches about taking pride in your craftsmanship. It teaches about being responsible and trustworthy. It isn't preachy but, instead, illustrates its points as a series of relatable anecdotes - inviting you to learn from the experiences (and mishaps) of others.

**_It is interesting._** 

It won't stick you in one chapter for a month trying to wrap your head around some three page long nigh-undecipherable block of pseudo code wondering how you would actually use the thing, ever, in an actual program you write. Instead, it will inspire you, and leave you thinking _"that's the kind of programmer I want to be."_ It will help you craft a career you're proud of.

**_It is pertinent._**

It will give you a window into practices that can guide you, and your career, towards productive and profitable paths and away from potential pitfalls. It will save your future self, over and over, from thinking _"I wish I'd known that years ago."_ It talks about technical debt. It talks about testing. It talks about design. It talks about ... so much. But, not in a "you should do this" way. In a "let me tell you about a shit festival and how and why doing X can help you avoid festivals of your own" way.

### **Two notes:**
- Be sure to get the 20th Anniversary Edition, it is an excellent update to an already excellent book
- The audio book version is fantastic, one of the best 'technical' audio books I've ever listened to - adding to, not detracting from, the source material

**The Pragmatic Programmer** gets my vote for the one book we should all read - because it's a book we all can read. It's a book that has something to say, something we can hear, for every single one of us.

&mdash; Peace


<span>Photo by <a href="https://unsplash.com/@clarktibbs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Clark Tibbs</a> on <a href="https://unsplash.com/s/photos/programming?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>