Platform journeys, big-tech organs, data mesh in practice, and the modern-data-stack reckoning — the senior/staff cohort.
Scoped to the system-design lens: the Financial Times' five-generation zero-to-hero, LinkedIn's control plane and Netflix's auto-remediation organs, data mesh from its founding paper through believers (Intuit, JPMC, Grab) and the skeptics' readiness test — and the modern-data-stack era told in primary sources, including the bundling debate this newsletter took part in.
Four organs and their failed naive versions: the control plane (vs the shared SDK), self-serve provisioning that makes mistakes hard, the diagnosis loop, and semantic self-serve consumption.
Provisioning a Kafka topic at your company takes nine days. Not because anything is slow — because it's a *negotiation*: a ticket to the infra team, a review queue, a back-and-forth about partitions, a password over a Slack DM. Multiply by thirty data systems — warehouses, OLAP stores, streams, search — each with its own team, its own tooling, its own queue. The company's response so far has been heroics and escalations. The platform answer is a set of *organs* — and each has a naive version that fails in a specific, documented way. What are the organs, and what kills the naive versions?
The full week 2 brief is part of LeetData Pro.
