Book · 1987
Peopleware
by Tom DeMarco
DeMarco and Lister time how long it takes a programmer to get back into the zone after one interruption, then build a whole management argument around that number.
What does Reddit think of Peopleware?
Three separate excerpts name this book directly, and they don't agree on what it argues. r/programming's ↑201 read is the management case: DeMarco and Lister's 'immersion time,' the cost of getting back into the zone after an interruption, framed as required reading for anyone managing developers. r/programming's ↑60 read is blunter: the book calls open-plan seating 'a plague upon the land,' full stop, from someone who read it in the late 1990s. r/cscareerquestions's ↑95 read complicates both: it cites the same book's research to argue open offices work fine up to twenty people on one goal, and only break down once multiple goals compete for the same room. That's not three people agreeing the book is anti-open-office. That's three people pulling different chapters. Mythical Man Month and DeMarco's own later book, Slack, show up in nearby threads, but neither is this title.
Community feedback & reader fit
Themes
- · open-plan office critique
- · immersion time and interruption cost
- · team goal alignment versus headcount
- · management reading for tech leads
- · workplace design as productivity lever
Common praise
- + r/programming's ↑201 thread treats the immersion-time chapter as required reading for anyone managing developers, not just a fun stat to cite.
- + The 'plague upon the land' line about open-plan seating gets repeated by someone who actually read the book in the late 1990s, not paraphrased secondhand.
- + r/cscareerquestions pulls a specific number out of it, twenty people on one shared goal, instead of a vague 'open offices bad' takeaway.
Common criticism
- − The book's own fans can't agree on what it says about open offices: one thread calls the layout a plague outright, another cites the same book to argue it works fine under the right conditions.
- − Reddit keeps reaching for the Mythical Man Month and DeMarco's own Slack in the same breath, so this title has to compete with adjacent classics for the same shelf space.
- − None of the three displayed excerpts push back on the book directly; the disagreement is between readers' summaries of it, not a documented critique of the book itself.
Who it's for
If you manage developers and have never quantified what an interruption costs, r/programming's ↑201 thread treats the immersion-time chapter as the reason to read this before your next org redesign. Open-plan skeptics get ammunition from the 'plague upon the land' line, quoted by someone who's carried it since the 1990s. If your team already works from the same floor toward one shared goal, r/cscareerquestions's research citation suggests the book's argument may not land the way it does for a multi-team office. Come for the office-layout chapter; the rest of the book covers hiring and team formation that these three threads don't touch.
Mentions over time
Which Reddit comments matter for Peopleware?
The most relevant excerpts across the subreddits where this book is mentioned — opinionated, argued takes first, then top-upvoted mentions. Click through to read the full thread.
“What I would call the classics: * Design Patterns - Elements of Reusable Object-Oriented Software * Code Complete * Rapid Development * The Pragmatic Programmer * The Mythical Man-Month * Operating Systems Design and Implementation * Refactoring - Improving the Design of Existing Code * The Algorith…
“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 * […
“Check out "Peopleware", a book from 1987. The authors either did the research themselves, or they referenced it. In that book, they referred to it as "Immersion Time", and used a figure of approximately 15 minutes. That "23 minutes and 15 seconds" thing looks like it's pretty clearly a joke. People …
“The author should read Peopleware. It contradicts a lot of what they say with actual data. Namely, projects without hard deadlines are completed faster. This is because arbitrary deadlines are some of the most demoralizing tools at an incompetent managers disposal. I will extend an olive branch thou…
“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 …
“The topic was covered in which I was reading as our company was rolling out high performance team pods. I ended up working a lot of nights between 9pm and 2am to get my thinking work done.
“And here’s the list for those too lazy to follow that link: 1. The Pragmatic Programmer 2. Clean Code 3. Code Complete 4. Refactoring 5. Head First Design Patterns 6. The Mythical Man-Month 7. The Clean Coder 8. Working Effectively with Legacy Code 9. Design Patterns 10. Cracking the Coding Intervie…
“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 …
“I’ve only been a dev for 3 years and I went to a technical school. The thing I would change would be my old attitude about computer science books. For … written from experts. They’re comprehensive and encapsulated. Meaning they are one cohesive experience rather than random sites filling in holes..…
“>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 can recommend *Peopleware: Productive Projects and Teams by Timothy Lister and Tom DeMarco*. It gives a good perspective on the role of people on software development, how to understand and handle the dynamics of teams and projects. Excellent book. Also, *Clean Coder by Robert Martin* teaches a l…
“From the excellent book Peopleware: > There are thousands of accounts receivable software out there. At this very moment there are tens more being developed. Some of these projects will fail.... It's clearly not the technology - so it must be the people." The whole book is about how to make the p…
“> I always take any opportunity to recommend the book Peopleware Productive Projects and Teams whenever I can. Peopleware: Productive Projects and Teams is a 1987 book on the social side of software development, specifical…
Convinced? Pick up Peopleware
Readers also mention
Books that share discussion threads with Peopleware — counted from the comments, not curated.
Peopleware — frequently asked
What does Peopleware actually say about open-plan offices?+
It depends which Reddit thread you trust. r/programming's ↑60 excerpt is blunt: the book calls open-plan seating 'a plague upon the land.' r/cscareerquestions's ↑95 excerpt cites the same book's research to say open offices work fine for up to twenty people chasing one goal, and only fail once multiple goals compete for the same space. Both cite Peopleware; they don't describe the same takeaway.
Is Peopleware just about office layout?+
No. r/programming's ↑201 thread centers on 'immersion time,' DeMarco and Lister's term for the cost of getting back into the zone after an interruption, and calls the chapter required reading for development managers. The open-office material is the part Reddit quotes most, but the excerpt itself frames the book as management reading, not interior design criticism.
Is Peopleware the same as The Mythical Man-Month?+
No, and they show up in the same threads for a reason: both get recommended alongside each other, but Mythical Man-Month is Brooks's book on why adding people to a late project makes it later, while Peopleware is DeMarco and Lister's book on interruption cost and office design. r/cscareerquestions's ↑76 excerpt recommends Mythical Man-Month specifically, not this title.
Should managers read Peopleware in 2026?+
The one displayed excerpt that frames it that way says yes without hedging: r/programming's ↑201 comment calls the immersion-time chapter 'required reading for anyone who wants to be a development manager at any level.' That's one thread's verdict, not a fleet consensus, but it's a specific, dated claim rather than a vague recommendation.