100 Books Like Peopleware

With this textbook disguised as a novel, Goldratt tells a story that sneaks up on you, revealing how simple digital thinking—like tracking bottlenecks and using systems analysis—can revolutionize physical processes. It’s not just about manufacturing; it’s about seeing challenges as opportunities to improve again and again.

This is a story about inspiration and being ready to look at the world differently to make every process—from your own projects to global operations—run a little smoother.

This book greatly influenced my philosophy around style. Norman's ostensible subject is the design of physical objects, like emergency exits, shower faucets, and refrigerators, but most of what he says is directly applicable to software design and API design, too.

For example: Whatever you expose or document about your interface, the user will take that and form a mental model of the implementation—and he'll program against that mental model, not against your documentation. So you'd better make sure that your interface—by exposing certain details and deemphasizing others, appropriate naming, and so on—suggests a mental model that will be useful to the user (even if it is not correct in every particular).

For example, a horizontal rod mounted on a door affords pushing (a bit of jargon that's entered my technical vocabulary), while a vertical rod affords pulling. If you use the design language of a horizontal rod, people will… show more.

Deming showed me how to think about organizational performance improvement. I was moving from a clinical psychologist in private practice to an organizational psychologist helping companies develop change strategies. I had studied and loved statistical variation in the context of scientific research, but not in the context of addressing real-world challenges. 

But Deming does something very surprising. He starts by understanding variation and then moves on to understanding organizational culture. Not the theoretical frameworks we all know, but the work world from the view of the front-line employee. Deming’s insight is that the central challenge of culture change is understanding the view of people closest to the work, the ones who perform operations.

They are not motivated by slogans and lofty ideas but by producing great products and services. Taking pride in the work they are doing is central to performance; lost by management fads and enhanced by doing it… show more.

We all know how important culture is to DevOps.

Well, Doug McGregor was one of the earliest proponents of healthy workplace culture. The Human Side of Enterprise was written during the 1950s and contains the kind of advice you might associate with Dan Pink’s more recent book, Drive.

If you want to read a book from the pivot point between command and control management and modern theories of motivation, this is the place to start.

The importance of Extreme Programming can’t be overstated.

Kent Beck created one of the few Agile methods that captured not just a process for managing work, but a set of practices that would keep your software manageable in the long run. Shortly after this book was published, the Agile Manifesto was created.

You might say, “the rest is history”, except the industry lost its way for a decade. Extreme Programming was revived in Dave Farley and Jez Humble’s Continuous Delivery – now a vital part of DevOps. The State of DevOps report has validated at least half of the Extreme Programming practices, and Continuous Delivery brings it to the fore once more.

I was lucky enough to read an early draft of this book and it’s simply the best analysis of the open-source software ecosystem around today.

The writing style is friendly and not formal despite the academic-level research that went into this book. It made me think differently about the open-source projects I maintain and how I interact and chose those I use.

This is from an older generation of open source development, pre-GitHub, but much of the advice here is still incredibly relevant and astute today, helping provide advice on the interpersonal as well as technical sides to open source development.

Many of the underlying principles from this book are what form my grounding as an open-source maintainer for the last 15 years.

Another book that predates GitHub but provides a lot of actionable advice today that’s been mostly ignored across much of our industry.

Hard problems like “why isn’t my software project reliable?” are tackled head-on and addressed here. It was an early nudge for me to automate as much as possible in software projects and not ignore difficult problems with project organisation in favour of “fun” technical tasks.

I work remotely most of the time, and leading virtual project teams (or any teams) is a real challenge. I used to be able to catch people in the office, but the world of work has changed now, and I have to rely on different strategies.

This book is packed with strategies and I enjoyed learning new ways of being able to connect with my teams even though we are no longer in the same office most of the time. The book taught me about having the right mindset for virtual leadership and I loved all the different case studies and stories that helped illustrate good (and not-so-good) ways of working. 

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.