The Death & Revenge of the Junior Developer
Read together, these two essays are a bet Yegge makes against himself. The first is a horror movie — junior developers written out of the story. The second is the sequel where the supposed victim turns out to be the one holding the high ground.
the death — why the role looked doomed
The 2024 essay opens on a grim market. When an LLM can turn a senior's intent into working code in seconds, the traditional junior job — being the cheap hands that write the obvious code — is exactly the job the machine does first. Yegge's framing is deliberately funereal.
"A lot of people picked a bad year to be a junior developer."— The Death of the Junior Developer
The mechanism isn't that AI is smarter than a senior. It's that AI amplifies whoever is already good at knowing what to ask for — and that skill is precisely what juniors haven't built yet. The tool rewards judgment you don't have.
"Chat, it seems, is safer for senior programmers than it is for junior ones."— The Death of the Junior Developer
CHOP — chat-oriented programming
This essay is the origin point of a term that stuck. Yegge names the new modality on the spot, correctly guessing he'd be repeating it for years:
"Chat-based programming, which I will preemptively label Chat Oriented Programming (CHOP) or just 'chop', because I suspect I'll be saying it a lot, is a brand-spanking new phenomenon."— The Death of the Junior Developer
The definition itself is short enough to memorize — the whole practice is directing an AI in natural language and steering it toward the code you want, rather than typing that code yourself:
"Briefly, CHOP is coding via iterative prompt refinement."— The Death of the Junior Developer, defining CHOP
The stakes he attaches to it are why the term matters: if CHOP wins, it doesn't just change how a few people work — it changes who, or what, writes most of the world's code.
"If chat-oriented programming becomes the dominant modality for programmers, then LLMs will be writing the vast majority of all source code worldwide."— The Death of the Junior Developer
the revenge — the reversal
The 2025 sequel is Yegge walking back the obituary. The thing he missed: adoption isn't distributed the way seniority is. The developers with the least to unlearn — and the least ego invested in typing code by hand — leaned into AI hardest.
"Junior developers have actually been far more eager to adopt AI than senior devs."— The Revenge of the Junior Developer
By 2025 the modality had also moved on from pure chat to agents — systems that take a task and run the loop themselves. In that world the operative skill is willingness to delegate and verify, not decades of hand-coding muscle memory. So the person Yegge had buried a year earlier turns out to be standing on top of the hill.
"Junior devs have the high ground, and the battle is now over."— The Revenge of the Junior Developer
what it means for how you level up now
The through-line across both essays is a shift in whose responsibility improvement is. The old career script waited for the model, the tool, or the senior to hand down capability. Yegge's version puts it squarely on you: the tool is here, it's good enough, and the only question left is whether you'll do the work of learning to wield it.
"It's not AI's job to prove it's better than you. It's your job to get better using AI."— The Revenge of the Junior Developer
- Learn to drive an agent, not just a chatbot. The 2025 skill is task delegation plus verification — hand the loop off, then check the work.
- Build the judgment CHOP rewards. "Iterative prompt refinement" only converges if you can tell good output from bad. That discernment is the whole game.
- Stop waiting for permission. The role isn't gone; the entry criteria changed. Adoption speed now beats tenure.
"Lean in. It's time. AI is here."— The Revenge of the Junior Developer