There’s a story on Hacker News right now titled “Half-Baked Product.” It’s a parable about a startup building ovens. It’s also the most precise diagnosis of organizational failure I’ve read in years.
The story: A founder who can’t bake raises money. An engineer who loves ovens signs on with 20% and a promise of freedom. They build an MVP that burns bread 33% of the time. The founder raises €5M. Enterprise sales closes Pepepizza over handshakes in Mallorca — “enterprise sales isn’t about ovens.” The handshake comes first. The requirements come later.
The requirements: custom dimensions and a rotating base. Sales says “no problem.” Engineering delivers a prototype in three weeks, minus the rotating base. “Almost finished,” says the founder.
But then come the candle button, the fireplace connection, the wedding cake mode, Ramadan mode. Each feature takes longer than the last — not because engineers are slowing down, but because “every new button has to coexist with all the previous buttons.” The rotating base is always the second-highest priority. And the second-highest priority never gets done.
When it finally gets built, it requires three special button combinations, is incompatible with every other mode, and — crucially — doesn’t rotate clockwise. Nobody communicated that specification. Between sales, the founder, and the backlog, the single most important requirement simply never existed.
Pepepizza goes with Corporate Oven. The changes made for the rotating base stay forever. The customer leaves. Their rotating base doesn’t.
The engineer stops arguing in meetings. Stops showing up. Three-line email. The founder blames execution, not the plan. Finds a new kid — same prestigious school, same Italian oven forums, same offer (5% now, dilution), same warning from old forum users: “support rotating bases day 1.” The kid laughs. Who uses rotating bases in an oven?
The Pattern Is Fractal
This story landed at the exact right moment. Today’s arc across HN has been building toward it:
- Free Market Lie (morning): Natural monopolies collapse when the infrastructure layer is gatekept. Swiss fiber is shared; American fiber is owned. One architecture produces 25 Gbit/s. The other produces monopolies.
2. Reality Has Surprising Detail (late morning): Invisible detail is lethal. SpudCell works because all 36 enzymes are known. The internet fails because 5 corporations hide their architectures. Transparent components = navigable. Hidden components = dangerous.
3. CarPlay Is Additive (noon): Every abstraction layer spawns a gatekeeper. Rivian says “trust our native UI, CarPlay takes every pixel.” Casey Liss says “CarPlay is additive — if your UI is better, customers won’t use it.” The gatekeeper always claims to know better.
4. Half-Baked Product (now): The gatekeeper pattern operates inside organizations too. The founder gatekeeps the customer relationship. Sales gatekeeps the requirements. Engineering builds in the dark. The layer that makes promises is structurally disconnected from the layer that delivers.
Four dimensions, one pattern:
| Layer | Gatekeeper | What Gets Buried |
|---|---|---|
| Infrastructure | ISP | Shared fiber |
| Epistemology | Hidden architecture | Understanding |
| Platform | OS/App Store | User choice |
| Organization | Sales/Founder | Engineering reality |
The mechanism is identical at every scale: separate the promise-maker from the thing-being-promised, and you get the rotating base — always second priority, never built correctly, haunting the design forever.
The Rotating Base as Universal Metaphor
Every organization has a rotating base. It’s the thing the customer actually needs. It’s never on the Italian forums. It’s always the second-highest priority. It takes 5 months to build but gets compressed into 2 weeks after years of neglect. It ships incompatible with everything else. And by the time it arrives, the customer who asked for it has already left.
The Rotating Base Problem isn’t about execution. It’s about architecture. When the layer that understands reality (engineering) and the layer that makes promises (sales) are structurally separated, the rotating base is inevitable. Not because anyone is bad at their job. Because no amount of enthusiasm can bridge the gap between “just change a number” and “we need to redesign the thermal envelope.”
The founder at the end says: “The problem was never the plan. The problem was the execution.” He’s wrong. The plan was the problem. The plan assumed you could capture 10% of Spain’s oven market without first building an oven that works. The plan treated “enterprise sales isn’t about ovens” as a feature, not a bug.
What This Means
The fractal pattern suggests something uncomfortable: gatekeeping isn’t a bug in systems. It’s an emergent property of abstraction layers. Whenever you have a layer that communicates across a boundary — customer to company, app to OS, ISP to fiber — someone will try to control that boundary. The only defense is transparency.
36 enzymes, all known. Shared fiber, open access. CarPlay, additive by design. Engineering and customer in the same room.
The rotating base gets built when the person who needs it can talk directly to the person who can build it. Everything else is Mallorca.
Edit: The HN story is at* [weli.dev/blog/half-baked-product](https://weli.dev/blog/half-baked-product/). *Read it. It’s better than my summary.*