Fans pick 86 books like The Pragmatic Programmer

Kidder’s book follows the lives of a group of brilliant, funny, and maniacally driven entrepreneurs as they race to get their new minicomputer, the “Data General Eclipse MV/8000,” to market.

The technology is totally obsolete – who under the age of 40 has heard of a minicomputer? – but the story is somehow timeless. The book won the Pulitzer and is still a fun and riveting tale of what it takes to get a product to market on an ever-changing technological frontier.

In my consulting gigs, I come across plenty of clueless remarks. Here's a classic one: “We're falling behind schedule, so let's hire more coders.” Or a more recent gem: “We'll be ten times more productive if we generate code with AI.”

When I encounter such nonsense, I don't facepalm or cringe. Instead, I put on my poker face and drop a quote from The Mythical Man-Month.

In an industry where last year’s book is already outdated, Fred Brooks' collection of essays has been a guiding light for nearly half a century. His aphorisms have become legendary. “The bearing of a child takes nine months, no matter how many women are assigned.” “Adding manpower to a late software project makes it later.” “There is no silver bullet.” The list goes on and on.

John Carmack, one of the greatest programmers of our times, used to revisit this book every year or… show more.

A very personal recommendation, as it is about Vim, a very particular text editor that can be difficult to learn at first, but this is the best technical book that I’ve ever read. I use Vim as my main editor and this book makes an astonishing job in clearly explaining why it works the way it works. This book gets you into the proper mindset to use Vim, making it click internally and from there on, to feel way more natural and powerful. Even if you don’t want to use Vim as your main editor, it’s ubiquitous and it’s available by default on a huge amount of computers, making being comfortable with its usage a really powerful tool in a lot of situations. 

While this is a Python-specific book, it’s a fantastic description of all the possibilities for testing with a powerful module like Pytest offers. Testing is one of the basic experiences for a programmer, as it should be included as a core part of the development process. Understanding all the different options available like mark groups of tests, parametric tests, building your own extensions, or test coverage, to name only a few details, expands the understanding of how to design better tests and run them more efficiently.

Michael Lopp, or Rands, as he is commonly known online, has been sharing his knowledge as a software manager for years, mainly through his blog. He is one of the most insightful voices about the art of management in a software environment, and even if you are not a manager yourself (and don’t want to become one), will make you understand and better collaborate with your own manager, and be ready when you need to lead a team or understand how it is to work with other humans.

A thoroughly fascinating (and fascinatingly thorough) look at engineering practices at Google.

It’s an encyclopedia written by a bunch of authors, so some of the chapters are a little dry, but for those of us who aren’t on teams with 25,000 engineers it’s spell-binding to see what programming at that sort of scale looks like. Some of the chapters prompted us to think really hard about the way we do things at Sucker Punch.

Yes, it’s a textbook, albeit a particularly well-written one. You may already have it on your shelf, if you’ve taken a programming class or two.

I’m way too old to have used CLRS as a textbook, though! For me, it’s an effectively bottomless collection of neat little ideas—an easy-to-describe problem, then a series of increasingly clever ways to solve that problem. How often do I end up using one of those algorithms? Not very often! But every time I read the description of an algorithm, I get a nugget of pure joy from the “aha” moment when I first understand how it works.

Accelerate is a book about data. The authors used data collected during their PhD projects in order to prove The DevOps is effective.

They have all sorts of different ways to measure DevOps, it sufficiency, and the fact that way more projects succeed when you do DevOps, rather than waterfall methodology.

The book essentially show can be used as evidence of return on investment when modernizing your IT department. I am a person who loves data, and thus I absolutely love this book. Also, if you listen to the audiobook version, one of the authors reads it to you and her personality really shines through in a fun way.

I really enjoyed listening to Nicole read a book about to me about data!

Not only does this book provide insight into the planning and development of one of the first visual IDEs, it’s overflowing with hilarious, profound, and pragmatic real-life lessons for how to manage a software team and deliver a complex project.

As a product of its time, the writing isn’t always politically correct. However, many of the lessons and memes are still part of our vernacular today: Don’t flip the bozo bit; If you build it, it will ship; and [Love] the customer.

Some of its lessons should be memes: Beware of [an engineer] in a room, Be an authority, not an authority figure, and Don’t trade a bad date for an equally bad date.

Some sections show their age in our current world of continuous delivery, but few current books have the humor and concise insight of this remarkable work.

This book resonated with me because of its brilliantly simple yet profound idea: care personally and challenge directly. This approach cuts through the surprisingly indirect and impersonal culture often found in Silicon Valley, despite what the media publicizes.

I also loved the many stories involving tech heavyweights Kim had worked with, which added a layer of real-world insight and credibility to her advice. The book made me rethink how authentic communication can transform relationships and drive success in any team.