The Mythical Man Month

“The great classic of software engineering, one of the few computer science books that repays frequent reading.”

Listed in the Programming section; singled out with the strongest endorsement on the page.

“My lists solely consists of books that skew oldish, but have aged well and continue to provide value today.”

Listed in Chen's 'Ten classic books that define tech' essay, which he describes as skewing 'oldish, but have aged well and continue to provide value today.'

“Arguably the only classic book in our field. If you haven't read it, shame on you.”

Listed on Atwood's 'Recommended Reading for Developers' on Coding Horror.

“everybody there had read The Mythical Man-Month, one of the classics of software management. (If you haven't read it, I highly recommend it.)”

From Spolsky's 2000 Joel on Software essay 'Painless Functional Specifications - Part 3: But... How?'; the book also appears on his Fog Creek management-training reading list.

“Reading it in 2026, we'll find some of it outdated, but it also retains many lessons that are still relevant today.”

From Fowler's bliki entry 'Mythical Man Month', where he calls conceptual integrity his most enduring lesson from the book.

“Data dominates. If you've chosen the right data structures and organized things well, the algorithms will almost always be self-evident. Data structures, not algorithms, are central to programming. (See Brooks p. 102.)”

Cited in Rule 5 of Pike's 'Notes on Programming in C' (1989); the page reference points to Brooks's Mythical Man-Month.