[{"data":1,"prerenderedAt":78},["ShallowReactive",2],{"term-t\u002Fthe-naming-police":3,"related-t\u002Fthe-naming-police":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-naming-police.md","The Naming Police",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 function works. The tests pass. The logic is sound. But the review has four comments, all about whether it should be 'getUserData' or 'fetchUserData.' The Naming Police is the reviewer whose entire contribution to any pull request is opinions about naming, delivered with total confidence and zero comments on whether the code actually does the right thing.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"The Naming Police is a colloquial term for a code reviewer who focuses disproportionately on naming conventions and style at the expense of reviewing logic, architecture, or correctness. Naming consistency has genuine value for readability, but when it becomes the sole focus of review, it can crowd out feedback that would catch actual bugs.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"The Naming Police struck again, four comments on variable names and nothing about the missing null check.\" \u002F \"I appreciate good naming feedback, I just want the Naming Police to also read the function body sometimes.\"",{"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 function works. The tests pass. The logic is sound. But the review has four comments, all about whether it should be 'getUserData' or 'fetchUserData.","beginner","md","t",{},true,"\u002Fterms\u002Ft\u002Fthe-naming-police",[49,50,51,52,53],"Nit","Bikeshedding","Code Review","Code Smell","Rubber Stamping",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Ft\u002Fthe-naming-police","LyKI3O8bAgmYQqzTe2nPa5myJqR4ydCRL4YZQNbI3iU",[61,64,68,72,75],{"title":50,"path":62,"acronym":6,"category":40,"difficulty":42,"description":63},"\u002Fterms\u002Fb\u002Fbikeshedding","The nuclear power plant committee approved the reactor design in 2 minutes — no one understood it well enough to debate. The bike shed for employees?",{"title":51,"path":65,"acronym":6,"category":66,"difficulty":42,"description":67},"\u002Fterms\u002Fc\u002Fcode-review","general","A code review is when another developer reads your code before it gets merged, looking for bugs, bad practices, or anything confusing.",{"title":52,"path":69,"acronym":6,"category":70,"difficulty":42,"description":71},"\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":49,"path":73,"acronym":6,"category":40,"difficulty":42,"description":74},"\u002Fterms\u002Fn\u002Fnit","A nit (short for nitpick) is a tiny, non-blocking code review comment about something that doesn't really matter but someone felt strongly enough to mentio...",{"title":53,"path":76,"acronym":6,"category":66,"difficulty":42,"description":77},"\u002Fterms\u002Fr\u002Frubber-stamping","Approving a pull request without actually reading the code. Just clicking 'LGTM' and moving on. We've all done it. We've all been burned by it.",1792528130615]