The Google Platforms Rant

Most "we should do X" memos are polite. This one is a rant — Yegge says so himself — and it lands because it's specific. He isn't asking Google to be more ambitious; he's telling it that the thing it's already worst at is the thing that's about to matter most, and he has an ex-employer's playbook to prove the point.

The thesis

Yegge's whole essay turns on a distinction between a product — a thing you build and ship to users — and a platform — a thing other people build on. Google, he argues, is world-class at the first and allergic to the second. The clearest tell is Google+, launched that same year as a direct answer to Facebook:

"Google+ is a knee-jerk reaction, a study in short-term thinking, predicated on the incorrect notion that Facebook is successful because they built a great product."— Stevey's Google Platforms Rant

The mistake, in his telling, is copying the surface. Facebook wins because it's a platform other companies build businesses on top of — not because its product is prettier. And that leads to the line the whole rant is built to deliver:

"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."— Stevey's Google Platforms Rant

The Bezos mandate

To show what platform discipline actually costs, Yegge tells an Amazon story. Some time around 2002 — he flags that the date is his own hazy recollection, give or take a year — Jeff Bezos issued a memo that reorganized how every team at the company was allowed to communicate. Six points, and the last one is the one everybody remembers:

1. All teams will henceforth expose their data and functionality through service interfaces.

2. Teams must communicate with each other through these interfaces.

3. There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team's data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network.

4. It doesn't matter what technology they use. HTTP, Corba, Pubsub, custom protocols -- doesn't matter. Bezos doesn't care.

5. All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.

6. Anyone who doesn't do this will be fired.— Stevey's Google Platforms Rant, quoting Bezos's mandate

Point 5 is the whole game. It isn't "build services" — plenty of companies do that. It's every interface, with no exceptions, designed as if a stranger on the open internet will one day call it. That single constraint is what quietly turned Amazon's internal plumbing into a product it could sell to the rest of the world. Yegge is blunt about the contrast with his current employer:

"Amazon does everything wrong, and Google does everything right."— Stevey's Google Platforms Rant

The joke underneath it: Amazon, the company that gets so much wrong, stumbled into the one discipline that mattered — while Google, which gets so much right, keeps skipping it.

The accessibility turn

Here's the move that makes the rant more than an org-chart complaint. Yegge names the property that a platform-ized product has and a merely-good product lacks. It isn't a UI feature or a marketing strategy — it's whether the thing can be reached and used by people and programs you never anticipated:

"There's actually a formal name for this phenomenon. It's called Accessibility, and it's the most important thing in the computing world. The. Most. Important. Thing."— Stevey's Google Platforms Rant

He means the word in its widest sense — not just accommodating disability (though that's part of it), but the general property that your system is reachable, programmable, and open to uses its authors didn't foresee. Dial Accessibility to zero, he argues, and you don't have a locked-down product — you have no product, because nobody can get in. That reframes Bezos's point 5: "designed to be externalizable" is just Accessibility enforced at the architecture level, on pain of being fired. And it's precisely the thing Yegge thinks Google, for all its engineering firepower, has never taken seriously.

Why it still matters

Fifteen years on, the rant reads like a prophecy that already came true. AWS became Amazon's profit engine; "everything is a service" stopped being a Bezos edict and became the default shape of software — microservices, public APIs, developer platforms as a business model. The vocabulary Yegge was reaching for is now just how the industry talks. His diagnosis of the underlying culture gap is the part still worth carrying:

"We don't understand platforms. We don't "get" platforms."— Stevey's Google Platforms Rant

The durable lesson isn't "build an API." It's the ordering: if you design every interface from the start as though an outsider will depend on it, the platform is a byproduct of good discipline rather than a project you have to launch. If you bolt access on afterward — the way most product companies do — you get a demo, not an ecosystem.

The one honest caveat

Yegge would be the first to flag the asterisks, and mostly did. He labels the piece a rant, not analysis, and it argues by assertion and anecdote rather than evidence — a first-person polemic aimed at colleagues, complete with the one-sidedness that implies. The Bezos-mandate details are his memory of a memo he didn't write and can only place at "around 2002, plus or minus a year," so treat the six points as faithful-in-spirit rather than a photographed document. And the whole thing reached the public by accident — it was meant to be an internal Google+ post — which is worth remembering when reading how freely he grades his own employer. None of that dents the core claim; it just means the rant's power is in its argument, not its footnotes.