No Silver Bullet—Essence and Accidents of Software Engineering.¶
Brooks, F. P. (1987). No Silver Bullet—Essence and Accidents of Software Engineering. Information Processing 86, 20(4), 1069-1076.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Accidental Vs Essential Complexity
- The distinction was formalized in software engineering with the argument that no single advance would deliver an order-of-magnitude improvement, because the essential complexity — the conceptual structure of the problem itself — was already dominant and could not be eliminated by tooling.
This sourceFormalizes the essential/accidental complexity distinction and argues that, accidental complexity having been substantially attacked, the dominant essential complexity precludes any single advance delivering an order-of-magnitude productivity gain.
- The distinction was formalized in software engineering with the argument that no single advance would deliver an order-of-magnitude improvement, because the essential complexity — the conceptual structure of the problem itself — was already dominant and could not be eliminated by tooling.
Mechanisms¶
- Essential-Accidental Complexity Audit
- Its four-way scheme is a direct descendant of the essential-versus-accidental distinction that has organized thinking about software difficulty for decades.
This sourceThe audit's rubric operationalizes exactly that split, adding "mixed" and "unresolved" to handle the cases Brooks's binary leaves ambiguous.
- Its four-way scheme is a direct descendant of the essential-versus-accidental distinction that has organized thinking about software difficulty for decades.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:fd11a00e8617 · see in the full table