rcmnd

The Mythical Man-MonthBook

by Frederick P. Brooks, 1995

Who uses, recommends or left The Mythical Man-Month, in their own words: each a verbatim quote with a link to where it was said.

8 people

Software design writer and chief scientist at Thoughtworks; wrote Refactoring and Patterns of Enterprise Application Architecture.
lovedaffiliate link

This point of view has been a strong influence upon my career, the pursuit of conceptual integrity underpins much of my work. The anniversary edition of this book is the one to get, because it also includes his even-more influential 1986 essay “No Silver Bullet”.

A bliki entry on Fred Brooks's The Mythical Man-Month and the lesson of conceptual integrity.

2026-05-05·martinfowler.com ↗

Executive coach for product leaders; previously a product partner at GV and a product manager at Google.
lovedaffiliate link

If you could only read one computer science book, this would be it. Almost fifty years old, it’s as relevant as ever. I promise you’ll nod your head as Brooks skewers mistakes that engineering leaders continue to make to this day.

From “Best Books for Product Managers [2026]”, his standing list, introduced as “the 44 books I’d consider essential to any PM’s bookshelf”. Marked TOP PICK on the page. Every book links through amzn.to and a Bookshop.org affiliate id (/a/83161/).

2026-01-07·bringthedonuts.com ↗

Engineering leader and writer; wrote An Elegant Puzzle, Staff Engineer and The Engineering Executive's Primer
loved

The first professional book I ever read, opening my eyes to the wealth of software engineering literature waiting out there.

His blog post collecting the management and leadership books that most changed how he thinks, ranked by value

2018-07-24·lethain.com ↗

Software engineer working on distributed systems and databases; creator of the rqlite distributed SQLite database.
loved

The amazing thing about The Mythical Man Month is that it doesn't feel dated, even though it was first published in 1975. Instead it simply feels like a group of programmers discussing the very same challenges the industry has today, with just different technology in use.

A post written after colleagues asked him which programming books had shaped him most.

2016-11-25·philipotoole.com ↗

Swedish programmer with degrees in engineering and psychology; author of Your Code as a Crime Scene and founder of CodeScene.
recommended

First, Refactoring, Domain-Driven Design, and the Pragmatic Programmer are all classics for a reason. Amazing books, and mandatory reads. Working Effectively with Legacy Code deserves all its praise, and of course everyone (yes, really) should check out the Mythical Man-Month.

A post naming the pre-2015 programming books that changed how he thinks about code, plus his take on the usual classics.

2026-08-11·adamtornhill.substack.com ↗

Computer performance engineer; author of Systems Performance and BPF Performance Tools.
recommendedaffiliate link

The Mythical Man-Month - Frederick P. Brooks (Addison-Wesley, 1995/1975)

His Books page, which he introduces as a list of textbook recommendations — explicitly not everything he owns, only what he would recommend. Last updated 24-May-2025. The Amazon links on the page carry an affiliate tag.

2025-05-24·brendangregg.com ↗

Software developer and writer; co-founder of Stack Overflow and Discourse, author of the Coding Horror blog.
recommended

I challenge any developer to pick up a copy of The Mythical Man Month and not find this tale of a long-defunct OS, and the long-defunct team that developed it, startlingly relevant.

His long-running "Recommended Reading for Developers" list, last updated September 2025.

2004-02-02·blog.codinghorror.com ↗

Programmer and writer. Keeps a running list of the non-fiction he reads, starring the ones he recommends.
read

A very old book about the practice of software development. Interesting both how much and how little has changed since the 70s.

On his public list of books he has read, with his notes.

2015-01-01·radex.io ↗

Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.

The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.

A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.

The shading behind a date shows how dated a recommendation is for its kind of thing.

The shading behind a date shows how dated a recommendation is, for its kind of thing. Fully green is recent. It drains a quarter at a time as the post gets older, and is empty once it reads as dated.

What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The shading is gone after about:

Stripes mean the post carries no date and the date shown is an estimate. No date at all, no shading.