[{"data":1,"prerenderedAt":78},["ShallowReactive",2],{"term-t\u002Fthe-todo-from-2019":3,"related-t\u002Fthe-todo-from-2019":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-todo-from-2019.md","The TODO From 2019",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",{},"'TODO: fix this properly.' No name, no ticket, no context, just sitting there in the code, older than half the people currently working on the file. The TODO from 2019 is the fossil record of every good intention a team has ever had and never followed through on, preserved forever in a comment nobody has the courage to delete.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"The TODO from 2019 is a stand-in for any long-abandoned inline comment marking intended future work that was never scheduled, tracked, or completed. Unlinked TODO comments tend to accumulate indefinitely because removing them feels riskier than leaving them, even though most are effectively permanent once they survive their first year unaddressed.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Found another TODO from 2019 today, right next to one from 2017.\" \u002F \"Either turn the TODO into a ticket or delete it, don't let it become the TODO from 2019.\"",{"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","'TODO: fix this properly.' No name, no ticket, no context, just sitting there in the code, older than half the people currently working on the file.","beginner","md","t",{},true,"\u002Fterms\u002Ft\u002Fthe-todo-from-2019",[49,50,51,52,53],"Technical Debt","Legacy Code","Backlog","Comment Archaeology","Code Smell",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Ft\u002Fthe-todo-from-2019","RhSZkH7l56UvHHQq-etcW_2V3TaKPC4t7jv5kLzXCRQ",[61,65,69,72,75],{"title":51,"path":62,"acronym":6,"category":63,"difficulty":42,"description":64},"\u002Fterms\u002Fb\u002Fbacklog","general","The backlog is the master to-do list for a product — every feature, bug, and idea that hasn't been built yet, prioritised by importance.",{"title":53,"path":66,"acronym":6,"category":67,"difficulty":42,"description":68},"\u002Fterms\u002Fc\u002Fcode-smell","architecture","Code that works but feels... wrong. Like when food smells slightly off — it might be fine, but something isn't right.",{"title":52,"path":70,"acronym":6,"category":40,"difficulty":42,"description":71},"\u002Fterms\u002Fc\u002Fcomment-archaeology","The code makes no sense until you find the one comment, buried two functions away, written five years ago, that explains it was built this way because of a...",{"title":50,"path":73,"acronym":6,"category":63,"difficulty":42,"description":74},"\u002Fterms\u002Fl\u002Flegacy-code","Old code that nobody wants to touch but everyone depends on.",{"title":49,"path":76,"acronym":6,"category":40,"difficulty":42,"description":77},"\u002Fterms\u002Ft\u002Ftechnical-debt","Technical debt is the coding equivalent of putting things on a credit card.",1792528130784]