[{"data":1,"prerenderedAt":79},["ShallowReactive",2],{"term-b\u002Fbig-ball-of-mud":3,"related-b\u002Fbig-ball-of-mud":60},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":54,"sitemap":55,"stem":58,"subcategory":6,"__hash__":59},"terms\u002Fterms\u002Fb\u002Fbig-ball-of-mud.md","Big Ball of Mud",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"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.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"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.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"The codebase is a Big Ball of Mud — nobody knows how anything works.\" \u002F \"Without consistent architectural discipline, every system trends toward Big Ball of Mud.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"architecture","Big Ball of Mud is the ultimate architectural anti-pattern — a system with no recognizable structure at all.","intermediate","md","b",{},true,"\u002Fterms\u002Fb\u002Fbig-ball-of-mud",[49,50,51,52,53],"Anti-Pattern","Spaghetti Code","Technical Debt","Refactoring","Strangler Fig Pattern",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Fb\u002Fbig-ball-of-mud","ZS7-MGqTJMteFfChSQAXdJk_TZjQa7c7ccg3GPNt_WY",[61,65,68,72,76],{"title":49,"path":62,"acronym":6,"category":40,"difficulty":63,"description":64},"\u002Fterms\u002Fa\u002Fanti-pattern","beginner","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.",{"title":52,"path":66,"acronym":6,"category":40,"difficulty":63,"description":67},"\u002Fterms\u002Fr\u002Frefactoring","Refactoring is improving the internal structure of code WITHOUT changing what it does from the outside.",{"title":50,"path":69,"acronym":6,"category":70,"difficulty":63,"description":71},"\u002Fterms\u002Fs\u002Fspaghetti-code","vibecoding","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.",{"title":53,"path":73,"acronym":6,"category":40,"difficulty":74,"description":75},"\u002Fterms\u002Fs\u002Fstrangler-fig-pattern","advanced","Replacing a legacy system piece by piece instead of doing a risky big-bang rewrite.",{"title":51,"path":77,"acronym":6,"category":70,"difficulty":63,"description":78},"\u002Fterms\u002Ft\u002Ftechnical-debt","Technical debt is the coding equivalent of putting things on a credit card.",1776518260008]