No Silver Bullet: Essence and Accidents of Software Engineering

The companion to The Mythical Man-Month. Brooks distinguishes essential complexity (inherent in the problem) from accidental complexity (introduced by our tools and processes). His prediction — that no single technology would deliver an order-of-magnitude improvement in software productivity — has held for four decades. For product directors who are told that AI, low-code, or the next framework will "10x" their teams: this paper explains why the bottleneck is always in the thinking, not the typing. Brooks's distinction between essence and accident remains the clearest framework for deciding where to invest engineering effort and where not to.