The Mythical Man-Month by Frederick P. Brooks — Summary, Key Ideas & Quotes

Brooks' most famous observation is that adding manpower to a late software project makes it later. This is because software development is not a simple matter of dividing tasks among more people; communication overhead grows rapidly as team size increases, and new members require time to get up to speed. The 'mythical man-month' is the mistaken belief that effort (measured in person-months) and schedule are interchangeable. In reality, some tasks are sequential, not parallelizable, and adding people often creates more coordination problems than it solves.

Brooks likens software engineering to a tar pit where both the small and mighty can get stuck. The complexity arises not just from the technical challenge, but from the essential difficulties of communication, specification, and change. He distinguishes between accidental difficulties (those that can be reduced with better tools) and essential ones (inherent to the nature of software). This metaphor highlights why software projects are uniquely prone to overruns and disappointments.