Big Ball of Mud¶
Foote, B., & Yoder, J. (2000). Big Ball of Mud. Pattern Languages of Program Design 4.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Anti-Pattern Catalog
- Its failure mode is anti-pattern zealotry: once every difficulty has a scary name, the catalog becomes a cynicism engine and every hard project gets branded a Big Ball of Mud
This sourceNames the BIG BALL OF MUD: "a casually, even haphazardly, structured system" whose organization "is dictated more by expediency than design."
- Its failure mode is anti-pattern zealotry: once every difficulty has a scary name, the catalog becomes a cynicism engine and every hard project gets branded a Big Ball of Mud
- Dependency Simplification Map
- Systems left to grow by accretion produce exactly this kind of unmapped tangle, and the map's danger is lending it false legibility.
This sourceExplains that piecemeal growth and repeated expedient repair can erode system structure into a Big Ball of Mud.
- Systems left to grow by accretion produce exactly this kind of unmapped tangle, and the map's danger is lending it false legibility.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:e7cf7cf1398c · see in the full table