Frederick P. Brooks Jr. wrote The Mythical Man-Month out of failure—specifically, the famously delayed IBM OS/360 project.

What he produced isn’t a manual so much as a set of hard constraints: why adding more people to a late project makes it later, why communication overhead scales faster than output, why complex systems resist clean planning.

The book reads almost like anti-optimisation. There’s no fantasy of perfect coordination here—only trade-offs, bottlenecks, and the slow realisation that software isn’t just technical work but organisational behaviour. The famous essay “No Silver Bullet” sits at the centre: complexity is not a bug to be solved but a condition to be managed.

It’s dated in its examples, but not in its logic. If anything, it lands harder now—everything is bigger, faster, more distributed, and still subject to the same constraints. For die-hard tech heads this one, like me :)