Book · 1987
Peopleware
by Tom DeMarco
A 1987 management book that correctly predicted open-plan offices would destroy developer productivity — and is still being cited to prove it.
What does Reddit think of Peopleware?
Forty-four mentions across 7 subreddits, and Peopleware keeps getting pulled into conversations it didn't start. r/ExperiencedDevs leads with 19 mentions and broadly positive sentiment — the crowd there treats it as the book managers should have read before greenlighting the open floor plan. The ↑201 r/programming comment captures the canonical use case: someone spots an article about flow state or distraction costs and replies, simply, "This was covered in Peopleware. DeMarco & Lister, 1987." The ↑60 comment from the same sub calls open-plan seating "a plague upon the land" and notes we've known this for decades. r/cscareerquestions accounts for 8 mentions but sentiment there is neutral — the book gets cited as evidence in office-layout arguments rather than recommended on its own merits. Nobody there seems to be finishing it fresh. r/programming (13 mentions) mostly surfaces it in reading lists alongside The Pragmatic Programmer and Code Complete. Genuinely contested territory: beloved as institutional memory, invisible as an active read.
Community feedback & reader fit
Themes
- · Developer productivity and deep work
- · Open-plan office dysfunction
- · Management as environment design
- · Human factors in software teams
- · Organizational memory and repeated mistakes
Common praise
- + The immersion-time framing gives managers a number to attach to every interruption — and that number is uncomfortable.
- + r/programming regulars reach for it the moment any article rediscovers the zone, because the data was already there in 1987.
- + The open-office chapter gets cited verbatim in workplace arguments across r/ExperiencedDevs, which means the prose held up.
- + Shows up in almost every serious dev reading list alongside The Pragmatic Programmer and Code Complete — it has staying power that most management books don't.
Common criticism
- − The examples are dated enough that newer readers treat it as archaeology rather than prescription.
- − Gets lumped into reading lists without specific chapter recommendations, which suggests people know of it more than they've finished it.
Who it's for
If you're a dev lead who just got told the team is moving to hot-desking, this is the book you quote in the objection email. Technical managers at any level who want research-backed language for why interruptions are expensive — the immersion-time framework is the thing you're looking for. Pair it with something from the last decade if you want current org-design thinking. r/ExperiencedDevs reads it as required background, the way you'd read The Mythical Man-Month: not because you'll implement its exact prescriptions, but because not knowing it means you're relitigating solved arguments.
Mentions over time
Top subreddits
Which Reddit comments matter for Peopleware?
Top-upvoted quotes across the subreddits where this book is mentioned. Click through to read the full thread.
“Here's the list, for anyone interested in just that: 1. The Pragmatic Programmer by David Thomas & Andrew Hunt (67% recommended) 2. Clean Code by Robert C. Martin (66% recommended) 3. Code Complete by Steve McConnell (42% recommended) 4. Refactoring by Martin Fowler (35% recommended) 5. Hea…
“Here's my list of the classics: **General Computing** * But How Do It Know? - The Basic Principles of Computers for Everyone * The Elements of Computing Systems: Building a Modern Computer from First Principles * […
“This was covered in “Peopleware”. DeMarco & Lister, 1987. This book talked about “immersion time” (the time it takes to get into “the zone”), and quantifies the cost of distractions. It should be required reading for anyone who wants to be a development manager at any level.
“Microsoft used to do that, at least in the 90's. Google reversed the trend, hard, and Microsoft followed suit at some point later. There's actual research in the book Peopleware that up to 20 people working on the same thing, open offices really are great, but if you have multiple goals or more …
“Get a copy of the Mythical Man Month and leave it on their desk. Put a bookmark in at Chapter 2 from which the book gets its name. It starts out: > Good cooking takes time. If you are made to wait, it is to serve you better, and to please you. —MENU OF RESTAURANT ANTOINE, NEW ORLEANS > More soft…
“I’m a strong supporter of agile and scrum but think we’ve forgotten some of the lessons of the past. First, the importance of building Slack into the system (and I highly recommend Tom DeMarco’s book with that title) and the human side of development, especially the working experience of people who …
“>Check out a book called “Peopleware”. I read it in the late 1990s. It includes a chapter on the effect of workspace, based on the research of the era. The book describes open-plan seating as "a plague upon the land", and rightfully so. We've known about the issues surrounding open-plan seating f…
“I assume you mean programming books? Here's a list of books I plan to read eventually to try to get better myself: Designing Data Intensive Architectures Algorithm Design Manual by Skiena Domain Driven Design Design Patterns in C# by Steve Metsker
Convinced? Pick up Peopleware
Readers also mention
Books that share discussion threads with Peopleware — counted from the comments, not curated.
Programming Pearls
Jon Bentley
Jon Bentley's 1986 column collection teaches you to shrink a 75,000-word dictionary into a Bloom filter and estimate anything — one problem at a time.
The Clean Coder
Robert C. Martin
Uncle Bob's professionalism manual: say no to bad estimates, refuse death marches, and work the 40 hours then study on your own time.
The Mythical Man-Month
Frederick P. Brooks Jr.
Fred Brooks spent the 1960s building IBM's OS/360 and wrote down everything that went wrong — in 1975, and it still lands.
Code Complete
Steve McConnell
Steve McConnell's 900-page construction manual for software, ranked third on Reddit's canonical reading list and still cited 25 years after publication.
Refactoring
Martin Fowler
Martin Fowler's catalog of named moves for cleaning up code that already works, cited 116 times across Reddit in 7 years as the Clean Code alternative people actually prefer.
Working Effectively with Legacy Code
Michael C. Feathers
Michael Feathers wrote the book for the developer who just inherited 30 devs' worth of code across 5 years in 5 different styles and has to ship next quarter.
Peopleware — frequently asked
Is Peopleware still relevant in 2026?+
Yes, for a specific use. r/programming commenters (13 mentions) keep pulling it out whenever an article rediscovers flow state or open-office harm — because the research was already there in 1987. The ↑201 comment that just says "This was covered in Peopleware" is the template. It's a citation weapon more than a live playbook.
What does Reddit actually think of Peopleware?+
Broadly positive but not loud about it. Nobody hates it; not many people are actively finishing it.
Should I read Peopleware before or after The Mythical Man-Month?+
Either order works. Both get cited in the same r/cscareerquestions threads about management dysfunction — the ↑76 comment there recommends Mythical Man-Month for deadline arguments, while Peopleware covers the physical environment angle. They're complementary. If you're a dev lead facing an office-redesign fight, Peopleware is the more immediately useful weapon.
Which subreddits recommend Peopleware most?+
r/ExperiencedDevs by a wide margin — 19 of the 44 total mentions, with positive sentiment. r/programming (13 mentions) surfaces it mainly in reading lists alongside Code Complete and The Pragmatic Programmer. The other five tracked subreddits account for one mention each, mostly neutral, mostly one-off citations in larger threads.