[{"data":1,"prerenderedAt":81},["ShallowReactive",2],{"term-t\u002Fthe-quiet-refactor":3,"related-t\u002Fthe-quiet-refactor":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-quiet-refactor.md","The Quiet Refactor",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",{},"The ticket says 'add a cancel button.' The diff also, quietly, renames four variables, extracts a helper function, and deletes four lines of dead code nobody asked you to touch. The quiet refactor is smuggling a small cleanup into an unrelated change because you know if you proposed 'let's refactor this' as its own ticket, it would die in backlog grooming forever.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"The quiet refactor is the practice of making small, unrequested code improvements alongside an otherwise unrelated task, rather than proposing the cleanup as a separate, formally scoped effort. It works because small improvements attached to necessary changes rarely draw scrutiny, though it can also blur the scope of a pull request if taken too far.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"That PR was supposed to be one line, but I snuck in a quiet refactor while I was in there.\" \u002F \"Half our code quality improvements happen as quiet refactors, nobody schedules a cleanup sprint anymore.\"",{"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","The ticket says 'add a cancel button.","beginner","md","t",{},true,"\u002Fterms\u002Ft\u002Fthe-quiet-refactor",[49,50,51,52,53],"Refactor","Technical Debt","Pull Request","Scope Creep","Code Smell",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Ft\u002Fthe-quiet-refactor","tjf-Cq22T8utEnDjvLjI4csXjBDD-HtlEY5RroaAmqA",[61,65,70,75,78],{"title":53,"path":62,"acronym":6,"category":63,"difficulty":42,"description":64},"\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":51,"path":66,"acronym":67,"category":68,"difficulty":42,"description":69},"\u002Fterms\u002Fp\u002Fpull-request","PR","git","A pull request is like raising your hand in class and saying 'Hey, I made some changes — can someone check my work before we make it official?",{"title":49,"path":71,"acronym":6,"category":72,"difficulty":73,"description":74},"\u002Fterms\u002Fr\u002Frefactor","general","intermediate","Refactoring is cleaning and reorganizing your code without changing what it does — like tidying your room without throwing anything away.",{"title":52,"path":76,"acronym":6,"category":40,"difficulty":42,"description":77},"\u002Fterms\u002Fs\u002Fscope-creep","Scope creep is when a simple feature request slowly grows into rebuilding the entire application.",{"title":50,"path":79,"acronym":6,"category":40,"difficulty":42,"description":80},"\u002Fterms\u002Ft\u002Ftechnical-debt","Technical debt is the coding equivalent of putting things on a credit card.",1792528130697]