The Merge: Annual 12-Hour Purge of Code Review — Meme Explained
Level 1: One Day Without Rules
Imagine a classroom where every drawing has to be checked by the teacher before it goes on the wall, and the teacher is picky — wrong shade of blue, redo it. Now imagine the school announces that for one day a year, anyone can tape up anything, no questions asked. Glitter, scribbles, a drawing of the principal as a potato — all of it goes straight on the wall. The kids would count down the days. That's this joke: programmers normally have to get their work inspected before it counts, and this tweet dreams up one official day where everyone just slaps their work up unchecked. It's funny because the freedom sounds amazing for exactly twelve hours — and then someone has to look at that wall for the rest of the year.
Level 2: Pull Requests and Purge Rules
A few terms doing the heavy lifting here:
- A Pull Request (PR) is how you propose changes in version control systems like Git: you write code on a branch, then ask teammates to review and approve it before it merges into the main codebase.
- Code review is that approval step — a human reading your diff to catch bugs, security holes, and design problems before they reach production. Most teams enforce it with branch protection rules, so you literally cannot merge without an approval.
- Tech debt is the accumulated cost of shortcuts: hacky fixes, copy-pasted logic, missing tests. Like financial debt, it's fast now and expensive later — "interest" gets paid every time someone has to modify that code.
If you're early in your career, your first weeks probably involved waiting anxiously for a senior to review your PR, then pushing fix-up commits for comments like "rename this variable." That friction is exactly what this meme weaponizes. The tweet imagines suspending all of it — the approvals, the nitpicks, the protections — for one glorious half-day, the way The Purge movies suspend all laws for one night. The "(7a-7p)" detail is a nice touch: even fictional anarchy respects business hours.
Level 3: All Tech Debt Is Legal
"Once a year, for 12 hours (7a-7p), any Pull Request will be accepted without any review whatsoever. All tech debt is legal. Introducing: The Merge"
Matt Pennig's tweet works because it's barely satire. The Purge franchise posits that one annual night of lawlessness keeps society stable the other 364 days — and every engineer reading this knows their org already runs an informal, undeclared version of The Merge. It's called the Friday before a release deadline. Or the quarter-end crunch when the VP wants the feature shipped and suddenly "LGTM" appears on a 4,000-line diff eleven minutes after it was opened.
The joke skewers a real tension in code review culture: review is a gate, and gates create queues. PRs rot in review purgatory for days while reviewers context-switch, nitpick variable names, and relitigate architecture decisions that were settled in a meeting nobody documented. The fantasy of a sanctioned 12-hour window where everything merges isn't about chaos — it's about relief. It's the same psychological pressure valve The Purge promises: the rules are suffocating, so we ritualize breaking them.
There's a darker layer for anyone who's done time near a real codebase: technical debt is already legal. It gets merged every day, just with paperwork. The // TODO: fix before launch comment that survives five years. The @ts-ignore that ships because the deadline is real and the type error is "probably fine." The difference between Pennig's dystopia and your repo is that your repo spreads the purge across the whole year and calls it velocity. A senior engineer doesn't laugh at this tweet because it's absurd — they laugh because compressing all of it into one honest, scheduled window from 7a to 7p would arguably be more principled than the status quo.
And the inevitable epilogue, which the tweet politely omits: the other 8,748 hours of the year, when git blame becomes a forensic instrument and someone has to revert, hotfix, and write the incident retro for what got force-merged at 6:58pm.
Twelve hours of lawless merging, followed by twelve months of git blame tribunals
At 7:01 p.m., git blame stops being a command and becomes forensic evidence.
I don't get it
Better than github stale bot
Implying that you can't get LGTM from your lead any time of the year. Very low aura