[{"data":1,"prerenderedAt":79},["ShallowReactive",2],{"term-t\u002Fthe-untouchable-file":3,"related-t\u002Fthe-untouchable-file":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\u002Ft\u002Fthe-untouchable-file.md","The Untouchable File",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",{},"Everyone knows which file it is. It's thousands of lines long, has no tests, was last meaningfully edited by someone who left the company years ago, and the unofficial team policy is simple: if it's not on fire, nobody opens it. The untouchable file is the one part of the codebase that survives entirely on collective fear rather than good design.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"The untouchable file is a section of a codebase that developers actively avoid modifying due to its complexity, lack of tests, or history of causing incidents when changed, regardless of whether it actually needs updating. Its untouchable status often becomes self-reinforcing, since avoidance prevents the documentation, testing, and refactoring that would make it safe to touch.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"That's the untouchable file, we route around it instead of fixing it.\" \u002F \"Someone's finally brave enough to open the untouchable file, wish them luck.\"",{"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},"vibecoding","Everyone knows which file it is.","beginner","md","t",{},true,"\u002Fterms\u002Ft\u002Fthe-untouchable-file",[49,50,51,52,53],"Legacy Code","Load-Bearing Hack","Technical Debt","Code Rot","Big Ball of Mud",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Ft\u002Fthe-untouchable-file","hVUNz4nWDJ2EcxYbk6b2IRUFYhdJGcmVeFShfuY_4fg",[61,66,69,73,76],{"title":53,"path":62,"acronym":6,"category":63,"difficulty":64,"description":65},"\u002Fterms\u002Fb\u002Fbig-ball-of-mud","architecture","intermediate","Big Ball of Mud is the ultimate architectural anti-pattern — a system with no recognizable structure at all.",{"title":52,"path":67,"acronym":6,"category":63,"difficulty":42,"description":68},"\u002Fterms\u002Fc\u002Fcode-rot","Code rot is the slow decay of a codebase from neglect. Comments become lies. Dead code piles up. Conventions drift.",{"title":49,"path":70,"acronym":6,"category":71,"difficulty":42,"description":72},"\u002Fterms\u002Fl\u002Flegacy-code","general","Old code that nobody wants to touch but everyone depends on.",{"title":50,"path":74,"acronym":6,"category":71,"difficulty":42,"description":75},"\u002Fterms\u002Fl\u002Fload-bearing-hack","It was supposed to be temporary. It was written in an afternoon three years ago to unblock a launch.",{"title":51,"path":77,"acronym":6,"category":40,"difficulty":42,"description":78},"\u002Fterms\u002Ft\u002Ftechnical-debt","Technical debt is the coding equivalent of putting things on a credit card.",1792528130842]