Platform Engineering's Inferno
summary
Framed around Dante’s Inferno, the talk claims an internal platform must lower cognitive load, provide golden paths and measurable ROI; concrete tools cited include GitHub, CNCF projects and Kubernetes, and Backstage-style inner‑source. It reports a first platform as a catastrophic failure from no docs that drove teams to build a third, working platform, recommends the tiniest viable platform (sometimes just one repository and one CI/CD pipeline), advises surveys after iterations, and uses thresholds like “<3 teams: buy, >3 teams: build” and examples of 35–50 engineers.
AI-written summary · about
chapters (14)
- 0:00Platform Engineering's Inferno
- 2:11Internal Developer Platform
- 5:20Building without boundaries
- 7:06Overloading platforms with features
- 9:56Tool sprawl and developer overwhelm
- 12:05Platform decay and maintenance
- 14:10Developer resistance to change
- 17:16Platform engineering without ROI
- 19:44Developers vs platform initiatives
- 22:15Platform market fit failure
- 25:47Culture and platform success
- 28:16Q&A: Inner Source
- 31:01Q&A: Convincing CFO
- 34:09Q&A: Golden paths vs flexibility
related talks
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
33mThe Platform Engineering Journey
29mKeynote: Building Bridges with Platforms: The Role of the Platform Engineer
46mBeyond DevOps: How and Why Companies Converge on Platform Models
43mEngineering Platforms Evolved
32mPlatform Engineering Is Not About Tech
44mPlatform Engineering is All About Product
27mTurning Platform Engineering Work Into Business Value Leadership Understands