Brooks's Law Evolves for the AI Era
Brooks’s Law, articulated by Frederick P. Brooks Jr. in his 1975 book The Mythical Man-Month, states that adding manpower to a late software project makes it later. The law emerged from his experience managing the IBM OS/360 project. While AI agents sidestep some traditional bottlenecks—onboarding time, endless stand-ups, office politics—by becoming operational in milliseconds without demanding breaks, the core constraint remains intact.
Sequential work stays sequential. The “Baby Problem” persists: nine agents cannot deliver a baby in one month. Overhead shifted rather than disappeared; instead of managing people, teams now manage agents. Humans still define “done,” review code, catch hallucinations, and stitch pieces together.
Deploying nine autonomous agents against a single codebase without clear orchestration produces chaos—they rewrite each other’s work in rapid cycles. A 2026 reformulation of Brooks’s Law emerges: adding agents to a project with unclear requirements gets you the wrong answer faster.
Read the full article
Continue reading at Hacker News →This is an AI-generated summary. Read the original for the full story.