Everything You Need, Nothing You Don't: How Do You Actually Build a Lean Platform
summary
Panelists show how to audit and shrink platforms with concrete wins and failures: teams rip out a useless resource‑module layer from a three‑tier Terraform stack, replace Kubernetes with GitHub Pages for cheap static sites, and run ~120 clusters for ~30 customers with about eight engineers; a telemetry‑only usage detector fails and is replaced by a simple standardized questionnaire. Key practices: kill your darlings, measure actual usage, celebrate removals in changelogs, and insist on self‑service not keyholding so deployments don’t stall.
AI-written summary · about
chapters (10)
- 0:00Introduction and panel setup
- 1:28Defining a platform
- 8:55Why build platforms
- 13:48Evolving golden paths
- 20:14Subtracting features to stay lean
- 29:19Anti-patterns in lean platform building
- 33:17Identifying platform needs
- 34:20Platform team size
- 36:27Examples of platform failures
- 41:24Most important rule for lean platforms
related talks
33mWhy You Should Treat Your Platform as a Product
27mTurning Platform Engineering Work Into Business Value Leadership Understands
26mLessons Learned from 7 years of Running Developer Platforms
39mOpening Panel
33mLessons learned from 7 years of running developer platforms
30mDiscover Your Tailored Platform Strategy with Real World Practice
43mEngineering Platforms Evolved
46mWork It Smarter, Dev It Better, Ship It Faster, Test It Stronger