Brooks's Law as Revealed by the Scroll of Truth
Description
A four-panel comic meme in 'The Scroll of Truth' format. In the first panel, an adventurer in a cave finds a chest, exclaiming, 'I'VE FINALLY FOUND IT... AFTER 15 YEARS'. The second panel shows the character triumphantly holding up a glowing scroll, labeled 'THE SCROLL OF TRUTH!'. The third panel is a close-up of the scroll, which reads, 'Two developers does not do 2x the work'. In the final panel, the character, now labeled 'PROJECT MANAGER', angrily throws the scroll away, yelling 'NYEHHH'. This meme humorously illustrates the fundamental software engineering principle known as Brooks's Law, which states that adding more people to a late software project makes it later. It satirizes the common managerial fallacy of assuming that developer productivity scales linearly, ignoring the realities of increased communication overhead, coordination challenges, and the indivisible nature of many programming tasks
Comments
8Comment deleted
Two developers don't do 2x the work, but they can definitely generate 4x the merge conflicts
Telling the PM that two devs aren’t 2× output is like invoking Amdahl’s Law to someone who thinks adding a thread removes lock contention - only thing that scales linearly is the number of stand-up updates
"Next sprint planning: 'We're behind schedule, so we're adding three more developers. Also, we need everyone to sync daily on the new integration points.'"
Adding a second developer doubles the velocity estimate and the standup length; the only thing that actually ships 2x is the merge conflicts
This meme perfectly encapsulates Brooks' Law from 'The Mythical Man-Month': adding developers to a late project makes it later. The 'Scroll of Truth' reveals what every senior engineer knows - two developers don't produce 2x output due to communication overhead, knowledge transfer costs, code review cycles, merge conflicts, and architectural coordination. The project manager's violent rejection mirrors the all-too-common response when engineering reality conflicts with delivery timelines. It's the eternal struggle between O(n²) communication complexity and management's dream of linear scaling - a truth so uncomfortable it gets yeeted into the void every sprint planning
If headcount scaled like throughput, we’d call it SIMD; instead it’s Brooks’ Law - O(n^2) meetings, O(weeks) ramp‑up, and a negative speedup
PM math: 2 devs = 2x velocity. Systems math: you just added a communication edge, a write lock on the spec, and Brook’s Law to the sprint
15 years to unearth what every architect knows: Brooks was right, man-months are mythical