[{"data":1,"prerenderedAt":80},["ShallowReactive",2],{"term-d\u002Fdrive-by-review":3,"related-d\u002Fdrive-by-review":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\u002Fd\u002Fdrive-by-review.md","Drive-by Review",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 PR sat open for two days. Someone finally clicks in, leaves one comment about a variable name, hits approve, and disappears. They never looked at the actual logic. Drive-by review is code review as a driving test where the examiner glances at your mirrors and passes you without ever watching you merge.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"A drive-by review is a superficial pull request review where the reviewer engages with a small, low-stakes portion of the change, often naming or formatting, while approving the substantive logic without real scrutiny. It commonly results from review queue pressure and time constraints, and it provides a false sense of coverage since the PR shows an approval from a named reviewer.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"That was a drive-by review, he commented on one variable name and approved everything else.\" \u002F \"We need more than a drive-by review on the payment logic.\"",{"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},"general","The PR sat open for two days. Someone finally clicks in, leaves one comment about a variable name, hits approve, and disappears.","beginner","md","d",{},true,"\u002Fterms\u002Fd\u002Fdrive-by-review",[49,50,51,52,53],"Code Review","Rubber Stamping","Pull Request","Nit","LGTM",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Fd\u002Fdrive-by-review","MB5v6VM6-hIlYFJgGiTj0DmXi81jtPTbDqRBdPjuoKM",[61,64,69,72,77],{"title":49,"path":62,"acronym":6,"category":40,"difficulty":42,"description":63},"\u002Fterms\u002Fc\u002Fcode-review","A code review is when another developer reads your code before it gets merged, looking for bugs, bad practices, or anything confusing.",{"title":53,"path":65,"acronym":66,"category":67,"difficulty":42,"description":68},"\u002Fterms\u002Fl\u002Flgtm","Looks Good To Me","vibecoding","LGTM is the two-word code review approval that can mean anything from 'I carefully reviewed every line and this is perfect' to 'I glanced at the title and...",{"title":52,"path":70,"acronym":6,"category":67,"difficulty":42,"description":71},"\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":51,"path":73,"acronym":74,"category":75,"difficulty":42,"description":76},"\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":50,"path":78,"acronym":6,"category":40,"difficulty":42,"description":79},"\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.",1792528080408]