[{"data":1,"prerenderedAt":76},["ShallowReactive",2],{"term-r\u002Frefactoring":3,"related-r\u002Frefactoring":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\u002Fr\u002Frefactoring.md","Refactoring",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",{},"Refactoring is improving the internal structure of code WITHOUT changing what it does from the outside. No new features, no bug fixes — just making the code cleaner, clearer, and easier to maintain. Like reorganizing your closet: same clothes, easier to find things.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Refactoring is the process of restructuring existing code without changing its external behavior. Techniques include: Extract Method, Extract Class, Rename Variable, Replace Conditional with Polymorphism, and Move Feature. Should be supported by tests to verify behavior is preserved throughout.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Let's refactor this before adding the new feature.\" \u002F \"Refactoring should be a constant activity, not a one-time project.\"",{"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","Refactoring is improving the internal structure of code WITHOUT changing what it does from the outside.","beginner","md","r",{},true,"\u002Fterms\u002Fr\u002Frefactoring",[49,50,51,52,53],"Technical Debt","Code Smell","DRY","SOLID","Testing",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Fr\u002Frefactoring","-oNprQ_WL-UrNsQxxsAUBfAuP7b4Mm1HJqvD2akqqLM",[61,64,68,72],{"title":50,"path":62,"acronym":6,"category":40,"difficulty":42,"description":63},"\u002Fterms\u002Fc\u002Fcode-smell","Code that works but feels... wrong. Like when food smells slightly off — it might be fine, but something isn't right.",{"title":51,"path":65,"acronym":66,"category":40,"difficulty":42,"description":67},"\u002Fterms\u002Fd\u002Fdry","Don't Repeat Yourself","If you find yourself copy-pasting the same code in multiple places, STOP. Make it a reusable function instead.",{"title":52,"path":69,"acronym":52,"category":40,"difficulty":70,"description":71},"\u002Fterms\u002Fs\u002Fsolid","intermediate","SOLID is five rules for writing code that doesn't turn into a nightmare over time. Each letter stands for a different rule.",{"title":49,"path":73,"acronym":6,"category":74,"difficulty":42,"description":75},"\u002Fterms\u002Ft\u002Ftechnical-debt","vibecoding","Technical debt is the coding equivalent of putting things on a credit card.",1776518307119]