CONCEPT
Accidental Scaffolding
The paradox Brooks’s framework surfaces in the age of AI: the very waste that made software development slow also provided the time and proximity in which the understanding that software development requires was accumulated—and eliminating the waste eliminates the scaffold along with it.
Accidental scaffolding names the relationship between the two kinds of complexity that
Frederick Brooks distinguished in his 1986 essay “No Silver Bullet.”
Accidental complexity—the difficulty that arises from tools rather than from the problem itself—was always the target of improvement.
Essential complexity was always the hard thing, the irreducible difficulty of understanding the world well enough to build systems that serve it. Brooks treated them as separable: eliminate the accidental, and the essential remains unchanged, ready to be addressed directly. What the AI transition reveals is that the separability was always partial. The accidental complexity was not only a cost; it was also scaffolding—a structure within which essential understanding developed as a byproduct of the time spent in proximity to the problem. The developer who spent four hours debugging a data access layer was spending most of that time in involuntary proximity to the data model, and the proximity occasionally deposited a thin