Did You Check the PR? Junior Slides Over 'AI Did It'

Level 1: "The Dog Wrote My Homework"

A kid hands in homework and the teacher asks, "Did you check your work before turning it in?" The kid freezes — you can almost see the little buffering circle over their head — and then proudly announces, "My robot did it!" As if that settles everything. The joke is that naming whoever did the work doesn't answer whether anyone checked it — and the kid's cheerful confidence makes it funnier, because she clearly thinks she's found the perfect loophole. Every teacher, parent, and senior engineer has met this exact smile, and none of them have ever accepted it.

Level 2: PRs, Reviews, and Why "Check It Yourself First" Matters

A PR (pull request) is how code changes get proposed on platforms like GitHub: you bundle your edits (the diff) and ask teammates to review them before they're merged into the shared codebase. Code review is the inspection step — a senior or peer reads your changes, asks questions, catches bugs, and approves or requests changes.

The unwritten rule the meme hinges on: review your own diff before asking others to. Scroll through every changed line yourself. You'll catch leftover debug prints, accidental file deletions, and that config value you meant to revert. Skipping this step and shipping raw output from AI coding assistants — tools like Copilot that autocomplete or generate whole functions — is what people now call vibe coding: prompt, accept, push, hope.

The loading spinner in panel two is a UI element every developer knows — the little rotating circle shown while software is busy. Drawn over the junior's pause, it jokes that her brain is "processing" before producing the excuse.

Early-career translation: AI can absolutely write your starter code. But when your senior asks if you checked it, the only acceptable answers involve you, personally, having read every line — because in the merge history, the Author: field has your name on it, not the model's.

Level 3: Authorship Laundering at the Review Counter

The three-panel structure is doing surgical work on a very 2020s failure mode. Panel one: a wide-eyed chibi girl labeled junior peeks over a counter at a long-haired senior, who asks the question that has ended a thousand standups:

did you check the PR before??

Panel two is the masterstroke — the junior's closed fist hovers over an empty wooden tray with a loading spinner drawn above it. Not a thought bubble: a spinner. The visual gag is that the junior's accountability process is itself an async operation, buffering while it computes the cheapest acceptable answer. Panel three: she cheerfully presents the tray, which now reads "AI did it." Case closed, smile included.

What's being satirized is authorship laundering — the emerging belief that if Copilot or an LLM generated the diff, the human who opened the pull request is merely a courier and bears no obligation to have read it. This inverts the entire social contract of code review. A PR has always been an implicit assertion: "I wrote this, I believe it works, I'm asking for a second pair of eyes — not the first." Vibe coding breaks that contract silently. The reviewer thinks they're the safety net behind an author's judgment; in reality they're the only human who has ever read the code, doing first-pass comprehension at second-pass scrutiny levels. That asymmetry is how subtly wrong AI code — plausible variable names, confident comments, off-by-one in the pagination logic — sails into main.

The senior-side trauma here is real and compounding. Reviewing careful human code is collaboration; reviewing unread machine output is unpaid QA for a robot. And the incentive structure feeds it: juniors are graded on shipped tickets, AI assistants make tickets close faster, and "did you read your own diff" appears on no performance rubric anywhere. The cruelest irony is that "AI did it" doesn't even shift the blame anywhere useful — the model won't be in the incident retro, won't get paged, and won't apologize. Accountability isn't a property of authorship; it's a property of submission. You clicked "Create pull request." Congratulations: it's yours.