For twenty years Steve Yegge has written the long, funny, profane essays that engineers actually pass around — on platforms, on languages, on interviewing, and now on what AI does to the whole craft. This is a map of the big ones: one page each, the original pinned at the top, the best lines quoted.
stevey:~$which rant do you need today?
▲ amber = the classic rants — Amazon & Google years▼ cyan = the AI era — agents & the coding future
00 who is steve yegge
A career-long habit of thinking out loud, at length
Steve Yegge is a programmer who became famous for writing about programming — sprawling, opinionated, often hilarious essays that started as internal posts at Amazon, continued through thirteen years at Google, and now land on Medium from his years at Sourcegraph. The through-line isn't a topic; it's a voice: blunt, self-deprecating, willing to be wrong at volume.
The rant is his form. He'll take one idea — objects are overrated, Google doesn't understand platforms, AI is a bigger deal than you think — and chase it for five thousand words until it's either obviously true or obviously insane, sometimes both. The essays below split cleanly into two eras: the classic rants from his big-company years, and the AI-era writing he's best known for now. Each card opens a one-page explainer with the source pinned at the top.
How to read a Yegge essay: skim for the thesis (it's usually stated bluntly early), enjoy the detour (there's always a detour), and keep the one sentence everyone will quote. This map keeps that sentence for you on every page.
01 the classic rants · Amazon & Google years
The essays that made him a household name in eng
The pieces that got forwarded into every engineer's inbox in the 2000s and early 2010s — on architecture, languages, interviewing, and the culture of software itself. Each links to a one-page explainer.
Meant to be an internal Google+ post; posted publicly by accident. Argues Google never understood platforms the way Amazon did — anchored by the legendary "Bezos mandate" that every team expose its data and function through service interfaces, or be fired.
The line: "It's called Accessibility... The. Most. Important. Thing."
A fable about how Java forces everything to be a noun — an object — and treats verbs (the actual doing) as second-class citizens. The definitive rant on OOP overreach.
The line: Java is a kingdom where nouns rule and verbs are servants
Proposes that software engineers fall on a political spectrum — "liberal" vs "conservative" — not about politics but about risk: how much they trust code to be safe vs. how much they fear it breaking.
His semi-official prep guide for the Google interview — what to study, what they're really testing, and why the whole thing is a somewhat arbitrary hazing ritual you can still prepare for.
The advice: study like it's a final exam, because it is
A whirlwind, deeply opinionated tour of the major languages — C, C++, Lisp, Java, Perl, Python — praising and roasting each in turn. An early classic from the Amazon-blog days.
The verdict: every language is somebody's kingdom of nouns
02 the ai era · agents & the coding future
The writing he's best known for now
Since 2023 Yegge has been the loudest credible voice arguing that AI coding is a genuine step-change, not hype — coining vocabulary ("CHOP," "heresies," "dark factories") and, through 2026, publishing almost monthly. One page per essay below, the source pinned at the top. Grouped into the arguments, the Gas Town saga, and the book.
Three days after launching Gas Town: the next gains come from the colony, not a smarter solo agent — agents as "colony workers" on an emerging Orchestrator API.
The frame: "factory farming code" — and it's hella fun
Why AI progress feels flat even as it climbs — the Demand Horizon and the Discernment Horizon. The case for AI literacy and token thrift.
The line: "Superhuman means unverifiable."
▸ the Beads saga · memory for agents (the bd this repo runs on)
Before Gas Town there was Beads — a tiny git-backed issue tracker built for coding agents, because agents can't remember across sessions and markdown plans rot. It's the substrate the whole Gas Town stack sits on. (And the same bd tool this very site's repo uses for tasks.)
Agents have no memory between ~10-minute sessions — Memento in real life. Beads is a git/JSONL-backed, dependency-aware issue tracker they can actually query.
How to actually run it: plan outside then import, file lots of issues, keep the working set small, daily hygiene with bd doctor.
The honest bit: "a crummy architecture... that requires AI to work"
▸ the Gas Town saga · his agent-coding universe
A Mad-Max-flavored running project and metaphor: you command a swarm of coding agents through a "Mayor," and the essays build a whole world around it — heresies, dark factories, and a federated economy of trust.
His book with Gene Kim (foreword by Dario Amodei) — the durable method for building production software with agents.
The framework: FAAFO — fast, ambitious, autonomous, fun, optionality
03 recurring ideas
The concepts that show up again and again
Strip away the individual essays and a handful of ideas run through everything Yegge writes. These are the ones worth carrying around. Each points to the essay where it lives.
Platforms & the Bezos Mandate→ Platforms Rant
Great companies build platforms, not products — and the way you get there is to force every team to talk to every other team only through service interfaces. Amazon did it by fiat; most companies never do it at all.
Nouns vs Verbs→ Kingdom of Nouns
Some languages (and some minds) organize the world into things; others into actions. Over-index on nouns and you drown in ceremony — classes and factories for what should be a verb.
Liberal vs Conservative Engineers→ Mystery Machine Bus
A single axis — how much you trust code vs. fear it — quietly predicts your stance on types, tests, languages, and process. Most technical fights are really fights along this axis.
CHOP — Chat-Oriented Programming→ Junior Developer
Programming by directing an AI in natural language instead of typing the code yourself. The skill shifts from writing to specifying, reviewing, and steering.
Heresies→ Gas Town
A heresy is a compelling but false belief an agent forms about your specific codebase — and, unchecked, spreads and persists as other agents read and propagate it. Your onboarding docs are the immune system.
The Two Horizons→ Flat Curve Society
The Demand Horizon caps how much a smarter model can help you (your problems aren't hard enough); the Discernment Horizon caps how much of its help you can trust (you can't verify what's above you). Together, they flatten the curve.
04 the quotable yegge
He writes in lines you remember
A taste — the full, sourced collection lives on the quotes page.
"Superhuman means unverifiable."— The Flat Curve Society (2025)
"A product is useless without a platform, or more precisely and accurately, a platform-less product will always be replaced by an equivalent platform-ized product."— The Google Platforms Rant (2011)
"Agents are very approximate workers and they like to guess at stuff. They will often make wrong guesses about how your system is supposed to work."— Gas Town Emergency User Manual (2025)
Quotes are verified against the originals on the quotes page, where each links back to its source.
05 your reading log
How many have you read?
Tick every essay you've actually read — progress saved on this device. A completionist's checklist for the Yegge canon.
READ
0%
The Google Platforms Rant2011 · platforms & the Bezos mandate
Execution in the Kingdom of Nouns2006 · OOP overreach
Notes from the Mystery Machine Bus2012 · liberal vs conservative
Get That Job at Google2008 · interview prep
Tour de Babel2004 · the language tour
Cheating Is All You Need2023 · the AI opening shot
The Junior Developer, Dead & Reborn2024–25 · CHOP
Gas Town & the Heresies2025 · the agent field manual
The Flat Curve Society2025 · the two horizons
Software Survival 3.0Jan 2026 · the six levers
The Anthropic Hive MindFeb 2026 · the transparent swarm
The AI VampireFeb 2026 · who captures the 10×
Welcome to the WastelandMar 2026 · a thousand Gas Towns
Vibe MaintainerMar 2026 · agents as PR sheriffs
Gas Town: Clown Show to v1.0Apr 2026 · the Mayor grows up
Welcome to Gas CityApr 2026 · the dark-factory SDK
Vibe Coding (the book)2025 · with Gene Kim
The Last Technical InterviewMay 2026 · kill the whiteboard
Introducing BeadsOct 2025 · agent memory
The Beads RevolutionOct 2025 · git-native TODO
Beads Blows UpNov 2025 · going viral
Beads Best PracticesNov 2025 · how to run it
The Future of Coding AgentsJan 2026 · the colony
references · current as of July 2026
Where this came from
Every essay page pins its own primary source at the top and quotes the original directly. The canonical homes for Yegge's writing: