Drive-by Review
ELI5 - The Vibe Check
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.
Real Talk
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.
When You'll Hear This
"That was a drive-by review, he commented on one variable name and approved everything else." / "We need more than a drive-by review on the payment logic."
Related Terms
Code Review
A code review is when another developer reads your code before it gets merged, looking for bugs, bad practices, or anything confusing.
LGTM (Looks Good To Me)
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...
Nit
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...
Pull Request (PR)
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?
Rubber 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.