Steve Yegge is an American programmer and essayist whose two-decade sideline — writing profane, funny, structurally serious arguments about how software gets built — has repeatedly escaped its intended audience. An internal Amazon blog became a book; an internal Google memo became the industry's canonical platforms text; a late-career obsession with AI coding agents became a book, a toolkit, and a consulting practice. He is, by his own billing, forty years into writing code and still entirely unable to keep his opinions inside the company walls.
The career underneath the writing
His own history page tells it straight: five years of 8086 assembly at GeoWorks beginning in 1992, then Amazon starting December 21, 1998 — where he began as a technical program manager on the 1999 push to split the monolithic database into services, work he frames as the start of the migration that led to AWS, and ended as a Senior Manager running Customer Service Applications and developer-productivity teams. It was at Amazon, in summer 2004, that he started the internal "Developers Journal" blog that became Stevey's Drunken Blog Rants: about fifty late-night essays, republished publicly only after he left.
Google followed, 2005 to January 2018, in Kirkland. There he created Grok — the internal code knowledge graph later released as Kythe — ported Ruby on Rails to Mozilla Rhino after Google declined to adopt it, wrote js2-mode for Emacs, and spent roughly six years on the company's internal "Culture Club." He left in January 2018 for Grab, the Southeast Asian super-app, running engineering for Ads & Monetisation, Personalization, and Data Insights until Covid ended the travel in May 2020. Two-plus self-employed years on Wyvern — the online game he has built since 1995 — preceded Sourcegraph, where he joined as Head of Engineering in October 2022, stepped down to an IC role in February 2024 to get his hands dirty with AI on the Cody assistant, and left in November 2025 as the Amp division split off.
The rants
Three essays anchor the classic bibliography. "Tour de Babel" (2004) is a whirlwind, deliberately impolitic tour of programming languages and the cultures around them. "Execution in the Kingdom of Nouns" (2006) casts Java's object model as a kingdom where verbs are enslaved to nouns — an argument about how language structure deforms thought, dressed as a fairy tale. "Good Agile, Bad Agile" (2006) separates Google's emergent, bottom-up process from the methodology industry selling index cards to frightened managers. Around them sits a large body of essays on interviewing ("Get That Job at Google"), hiring, Emacs, and code size — plus the "Drunken Blog Rants" catalog he still maintains, self-scored with "called it" and "whiffed it" tags.
Then there is the rant that ate his biography. In October 2011, a roughly 3,700-word memo meant for Google colleagues went public on Google+ by mistake. Its argument — Amazon survived because Bezos mandated externalizable service interfaces; Google builds products but doesn't "get" platforms, and "a platform is accessibility" — landed alongside color like "Dread Pirate Bezos" and the verdict that Google+'s own platform was "a pathetic afterthought." The Washington Post called it his Jerry Maguire moment; Sergey Brin indicated he'd keep his job. The original is gone with Google+; the text survives on a much-starred GitHub Gist, which is itself part of the story.
The AI turn
At Sourcegraph he watched ChatGPT land six weeks into the job and pivoted hard. The May 2024 essay "The Death of the Junior Developer" argued that chat-oriented programming — CHOP — was already the present, and that engineers refusing it would be left behind. The reaction was furious, and he kept going: a book, Vibe Coding, with DevOps researcher Gene Kim (IT Revolution, October 2025), which The Register credited for candor about agents deleting test suites and nearly wiping repositories while questioning whether the gospel generalizes beyond operators like Yegge.
The practice now has tools. Beads (October 2025) is a version-controlled work ledger that gives agents durable memory — "adderall for your coding agent," he says, and his site reports 23,000-plus GitHub stars. Gas Town, open-sourced January 1, 2026, orchestrates dozens of parallel agents in what he calls a "dark factory," with a Mad Max lexicon — polecats, refineries, witnesses, a mayor — that he credits for making the system legible to humans and agents alike. Gas City (April 2026) splits the toolkit into a declarative SDK, and the Wasteland (March 2026) federates Gas Towns through a shared work board and portable reputation. All of it, he insists, is one-hundred-percent vibe coded — he has never read the code.
Since mid-2026 he has worked as an independent advisor and consultant on AI transformation, premised on a claim his whole career supports: companies are blocked not by the technology but by their culture.
The throughline
Read straight, the record is one long argument for leverage over ceremony: platforms over products, verbs over nouns, working process over purchased methodology, and now agent fleets over keystrokes — delivered in a comic register that makes the medicine go down and keeps the press quoting him.
What the record does not settle
His own pages disagree on whether Google ended in 2017 or January 2018, and on whether Grab began in 2017 or 2018; the likeliest reading is offer-versus-start rounding, but the index keeps the seam. Wyvern's founding and promised return are self-reported. The $GAS meme-coin episode — a third-party token named after Gas Town that routed fees to him, collapsed, and reportedly left him up more than $290,000 — rests on a single line of Bloomberg coverage cited by Wikipedia, and the primary piece is not in this catalog. And the "most-cited platforms text" framing is his own site's, echoed but never measured.
This index was compiled from public sources and does not imply the subject's endorsement. Citations live in the packet's source catalog.