Mythical Man-Month
A famous software-engineering principle that adding more people to a late software project makes it later, due to communication and coordination overhead.
As defined in Pieter Levels
Other definitions
Software development principle stating that adding more people to a project cannot accelerate it proportionally due to communication overhead and inherent sequential dependencies; 'nine women cannot have a baby in one month'.
Ben Horowitz and David Solomon: The Sweetest Macro Spot in 40 YearsFred Brooks' observation that adding people to a late software project makes it later, because communication overhead grows and engineering does not scale linearly.
Martin Casado on Frontier Model Economics, AI's Slowdown, and the Cursor Deal - [Invest Like the Best, EP.498]
Where it comes up · 3
- Bret Taylor - The Agent Era - [Invest Like the Best, EP.386]2 claims
- Ben Horowitz and David Solomon: The Sweetest Macro Spot in 40 Years1 claim
- Pieter Levels1 claim
Most important claims · 4 of 4Search all claims for “Mythical Man-Month” →
- The Mythical Man-Month is the myth, common among business-school-trained managers, that adding people speeds up a software project; often the inverse is true because small high-functioning teams hold complex systems in their heads, and adding people adds process and bureaucracy that disempower the most advanced technologists and slow things down.Bret Taylor - The Agent Era - [Invest Like the Best, EP.386]
- The famous Google Maps weekend rewrite was not a blank-slate miracle: the team's code base had become a mess of hard-won browser hacks after roughly six months of research-driven work, and Bret rewrote it by applying everything the team had learned, which cut the JavaScript bundle to about 20,000 uncompressed bytes and made it work reliably across browsers.Bret Taylor - The Agent Era - [Invest Like the Best, EP.386]
- Software development historically followed the 'mythical man-month' principle: nine women cannot have a baby in one month; you cannot accelerate product development by adding more engineers due to communication overhead and fundamental complexity limits.Ben Horowitz and David Solomon: The Sweetest Macro Spot in 40 Years
- One should be suspicious of more—more screens, more gear, more tools—because more can be defended with plausible productivity justifications yet often slows you down; constraints and condensing everything (e.g. working on a single laptop screen) can make you more productive than elaborate multi-screen battle stations.Pieter Levels