Drive-by Fix
ELI5 — The Vibe Check
A drive-by fix is when someone spots a bug, quickly patches it, and moves on without telling anyone — no ticket, no PR description, no context. The fix works, but six months later nobody knows why that weird if-statement exists. It's the coding equivalent of Batman — appears, saves the day, disappears into the night. Heroic but terrifying for maintainability.
Real Talk
A drive-by fix is an unplanned, minimally documented code change that addresses an incidental issue outside the developer's current task. While well-intentioned, drive-by fixes lack context (no ticket, brief commit message), skip testing, and can introduce subtle regressions. Teams should balance fix urgency with documentation and review requirements.
When You'll Hear This
"Someone did a drive-by fix on the auth middleware — no tests, no docs." / "If you spot a bug outside your task, file a ticket instead of doing a drive-by fix."
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.
Cowboy Coding
Cowboy coding is writing code with no rules, no process, no plan — just you, your editor, and the Wild West. No code reviews, no tests, no branches.
Hotfix
A hotfix is an emergency patch you ship immediately to fix a critical bug in production — no waiting for the next planned release.
Technical Debt
Technical debt is the coding equivalent of putting things on a credit card.