Big Ball of Mud
ELI5 — The Vibe Check
Big Ball of Mud is the ultimate architectural anti-pattern — a system with no recognizable structure at all. Not just spaghetti code but a full system where every part is tangled with every other part. It grows organically, survives on tribal knowledge, and adding any feature is a nightmare. Most legacy systems end up here.
Real Talk
Big Ball of Mud (Foote & Yoder, 1997) describes a software system lacking a perceivable architecture — a haphazardly structured, sprawling, sloppy mess. Despite being an anti-pattern, it's arguably the most common architecture because it emerges naturally from ad-hoc growth and deadline pressure.
When You'll Hear This
"The codebase is a Big Ball of Mud — nobody knows how anything works." / "Without consistent architectural discipline, every system trends toward Big Ball of Mud."
Related Terms
Anti-Pattern
Anti-Pattern is the opposite of a design pattern — it's a commonly used approach that looks like it solves a problem but actually makes things worse.
Refactoring
Refactoring is improving the internal structure of code WITHOUT changing what it does from the outside.
Spaghetti Code
Spaghetti code is code so tangled and messy that following the logic feels like untangling earphones that have been in your pocket for a week.
Strangler Fig Pattern
Replacing a legacy system piece by piece instead of doing a risky big-bang rewrite.
Technical Debt
Technical debt is the coding equivalent of putting things on a credit card.