Platform Engineering's Inferno
summary
An internal developer platform built on Kubernetes with APIs, CLI and UI plus CI/CD integrations (Argo/Flux/Jenkins), GitHub auth and an OpenTelemetry collector aims to cut cognitive load and preserve security; teams start with a test viable platform and golden paths, pilot one team, measure with DORA metrics and developer satisfaction, and show concrete wins (example: take a 15% deployment failure rate down to ~2%); favor small, iterative rollouts over big‑bang rewrites.
AI-written summary · about
chapters (15)
- 0:00Platform Engineering's Inferno
- 2:34Internal development platform
- 5:05Platform engineering Inferno
- 5:26Legacy devs and build vs buy
- 7:14Tool integration overload
- 8:38Options without guardrails
- 10:04Control and golden paths
- 12:55Pipeline migration friction
- 16:50Platform cost and justification
- 19:19Developer resistance and culture
- 21:26Lost developers and failure
- 22:07Navigating challenges
- 24:59Culture and build vs buy
- 27:05Measuring effectiveness
- 29:12Resources and credits
related talks
31m20k Leagues Under Platform Engineering
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
44mPlatform Engineering 101: Building Internal Developer Platforms
15mThe Art of Platform Engineering
39mPlatform Engineering as a (Community) Service
28mWhat's Next in Platform Engineering
37mAchieving High Performance with an Internal Developer Platform
29mIaC Next Steps in Platform Engineering