Essential vs. Accidental Complexity

Brooks's most consequential contribution to software engineering was a single analytical distinction drawn from Aristotle's metaphysics. Essential complexity arises from the problem being solved: requirements ambiguity, domain intricacy, institutional conformity, relentless changeability, and the invisibility of software as artifact. Accidental complexity arises from the tools used to solve it: programming languages, build systems, dependency management, framework conventions. The two respond to intervention differently. Accidental complexity can be reduced by better tools. Essential complexity cannot, because it is not a product of tools — it is a product of the world. The distinction matters because it determines what the silver bullet can and cannot reach. For forty years, every promised revolution addressed accidental complexity while leaving essential complexity untouched. AI has finally eliminated most accidental complexity, revealing essential complexity in a form stripped of its protective scaffolding.