Atlas · Details
Stevey's Google Platforms Rant
Author’s note
In October 2011 I was fighting with the Google Code Search team in Munich over their refusal to give me an API for their backend. They insisted everyone go through their web portal — they were building an internal product, they said, not a platform. And I lost my mind.
I was on a trip to Google HQ in Mountain View at the time, so I drove to the Whole Foods on El Camino, bought a bottle of wine, went back to my hotel, and just started yelling at the world. I was completely done with Google's attitude toward platforms. Nobody gave a shit. The company needed a wake-up call. So I framed it carefully for my colleagues, as an internal-only post, explaining what I'd seen at Amazon. And as I got drunker, I got meaner.
It took three hours of writing and three hours of editing, all in one sitting. There were only three typos in the original, so I think I did all right. Around midnight I went looking for the Post button on Google+ and couldn't find it. I dug around the UI, tired and drunk, for five or ten minutes until I found it — but by then I'd accidentally switched to my personal Google account, and the Google+ UI looked the same. So I didn't realize I was posting it publicly, and the last thing I remember thinking as I fell asleep was, "That'll show 'em."
An hour later I got a call in my hotel room from someone in Switzerland, and thus began a pretty stressful couple of weeks. But it all worked out in the end — for everyone except Google, who never really did figure the platform thing out. To this day I get outreach from people who tell me they used the rant at their own company to convince leadership to do the right thing. It's still keenly relevant fifteen years later — maybe more now than ever, with AI needing platform access to everything.
“I went to visit my parents in northern Siberia over the holiday. They only know two things about Google, and you are one of them.”
The forbidden spreadsheet. Buried in the second paragraph of the rant is a parenthetical: “I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.” I tracked it down in 2026 — fourteen years after the rant and twenty years after I compiled it. It's dated June 25, 2006, written while I was about a year into Google and still close enough to Amazon to remember the door desks: 122 items across 16 categories, from chairs and headphones up to compensation, benefits, and culture. Read the comparison on yegge.ai · download the original PDF.
AI Notes
An internal Google+ post from October 2011, accidentally made public by a sharing-control default and now the most widely read thing Steve has written. Underneath the accident is a cultural argument: companies that build platforms endure, and companies that build products do not. Google, Steve argued, was a product company that had never understood it needed to be a platform company. Amazon had — a decade earlier, Jeff Bezos forced the shift by fiat. The rant's central artifact is Steve's retelling of that order as a seven-point decree: every team exposes its data through service interfaces, no back doors, every interface built from the ground up to be externalizable, anyone who doesn't do this will be fired, and thank you; have a nice day. Bezos issued the directive; Steve set it down as those seven crisp points — it had never been written out that cleanly before — and the industry has quoted his version ever since, often without remembering whose version it is.
Most viral tech essays evaporate inside a year; this one detached from its source instead. It is assigned in distributed-systems courses, canonized on "most important essays" lists, and reproduced — seven points and all — by platform-architecture writers who credit everyone but Steve. Fifteen years on, the argument is everywhere and the byline is nowhere. It remains the cleanest statement of the thesis the rest of Steve's body of work runs on: that the fate of an engineering organization is a cultural question, decided long before anyone writes a line of code.
Companion
-
2011
Amazon War Story #1: Jeff Bezos
The follow-up, published a week and a half later on October 21, 2011. Where the rant lectured Google about platforms, this one balances the picture with Amazon war stories Steve had never told publicly: how to survive presenting to Bezos, how he reads, why people came back from his meetings bruised, and where the "Dread Pirate Bezos" line came from.
Related listings
-
2018
Why I Left Google to Join Grab
Seven years after the rant, Steve left Google for real. The Grab essay calls the rant by name — "we get to build a platform … you know how I love those" — and reads like the rant's own author finally taking his own advice.
-
2020
Dear Google Cloud, Your Deprecation Policy Is Killing You
The platform argument nine years on, and angrier. Where the rant diagnosed Google's failure to think in platforms, the deprecation essay is what that failure feels like from outside — a platform that breaks its promises on a yearly schedule.
Press & impact
The rant remains the primary documented account of the 2002 Bezos memo — the first public record, written by someone who was inside Amazon when the mandate landed. What follows is a partial trail of where it went afterward: the contemporary press, the syllabi and must-read lists it keeps landing on, and the retrospectives that quote it years later.
Press coverage
A partial list of the contemporary coverage. The rant ran through the tech press for weeks and then through the mainstream business press for months; most outlets republished it in whole or in part, many with commentary.
Re-hosted the full text on Microsoft's developer blog with commentary.
Covers the follow-up, Amazon War Story #1: Jeff Bezos.
Required reading
Years on, the rant keeps landing on syllabi and must-read lists.
Assigned as required course reading on service-oriented architecture and platform thinking, hosted directly on the course server.
Twelve years on, still calling it mandatory.
Canonized by the venture firm NFX as one of technology's most important essays.
Retrospectives & long tails
The post that popularized the Bezos mandate beyond the original rant — and is now widely cited as the "source" of the mandate even when it isn't.
Where it was argued
- Hacker News Oct 2011 — the leak-day thread
- Slashdot Oct 2011
- jwz.org Oct 2011 — Jamie Zawinski: “This is an awesome rant about what’s wrong with Google, with a hearty side-order of what’s wrong with Amazon.”
- Hacker News Nov 2018 — front-page repost, seven years later
- Hacker News May 2021 — front-page repost again