[{"data":1,"prerenderedAt":80},["ShallowReactive",2],{"term-t\u002Fthe-rewrite-graveyard":3,"related-t\u002Fthe-rewrite-graveyard":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-rewrite-graveyard.md","The Rewrite Graveyard",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",{},"There's a folder, or a branch, or sometimes just a Notion page, listing every attempt this codebase has survived to replace itself. Three rewrites, none shipped, all abandoned somewhere between 40 percent done and the next reorg. The rewrite graveyard is the quiet historical record of every time someone was sure a clean slate would fix everything.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"The rewrite graveyard refers to the accumulated history of abandoned rewrite or migration attempts within a long-lived codebase or organization, each typically started with genuine optimism and stalled before completion. It's a useful cautionary reference when a new rewrite is proposed, since the graveyard usually reveals the same underlying reasons previous attempts failed.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Before you propose another rewrite, go read the rewrite graveyard, we've been here three times.\" \u002F \"This is attempt four for the rewrite graveyard, same reasoning as the last three.\"",{"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","There's a folder, or a branch, or sometimes just a Notion page, listing every attempt this codebase has survived to replace itself.","beginner","md","t",{},true,"\u002Fterms\u002Ft\u002Fthe-rewrite-graveyard",[49,50,51,52,53],"Rewrite Syndrome","Second System Effect","Legacy Code","Strangler Fig Pattern","Technical Debt",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Ft\u002Fthe-rewrite-graveyard","1gXuwWc61BQ3aTxvK87s39lVnaX_4c-iKS8oDx2k9E4",[61,65,70,73,77],{"title":51,"path":62,"acronym":6,"category":63,"difficulty":42,"description":64},"\u002Fterms\u002Fl\u002Flegacy-code","general","Old code that nobody wants to touch but everyone depends on.",{"title":49,"path":66,"acronym":6,"category":67,"difficulty":68,"description":69},"\u002Fterms\u002Fr\u002Frewrite-syndrome","architecture","intermediate","Rewrite syndrome is the near-universal engineering urge to throw out existing code and start over. 'It would be so much cleaner if we rewrote it in Rust.",{"title":50,"path":71,"acronym":6,"category":67,"difficulty":68,"description":72},"\u002Fterms\u002Fs\u002Fsecond-system-effect","The second system effect is when you rewrite a successful system from scratch and massively over-engineer it.",{"title":52,"path":74,"acronym":6,"category":67,"difficulty":75,"description":76},"\u002Fterms\u002Fs\u002Fstrangler-fig-pattern","advanced","Replacing a legacy system piece by piece instead of doing a risky big-bang rewrite.",{"title":53,"path":78,"acronym":6,"category":40,"difficulty":42,"description":79},"\u002Fterms\u002Ft\u002Ftechnical-debt","Technical debt is the coding equivalent of putting things on a credit card.",1792528130720]