3 Ways You’re Screwing up Platform Engineering – And How to Fix It
summary
Three concrete failure modes and how to fix them are described with examples and numbers: Kubernetes/Kafka/Istio power tools create months of friction, generate high unplanned work and platform cost so teams migrate to lighter runtimes like Kinesis and Fargate and platform team does the lift and shift; technology anarchy shows 3+ stacks and 20 teams wasting time so leadership sets a Python pipeline template and paved roads for alignment; ticketing hell includes 11 week access waits, so high‑demand tickets become self‑service automations with audit trails.
AI-written summary · about
chapters (7)
- 0:00Intro
- 3:36What is platform engineering?
- 5:37No. 1: Power tools
- 18:32No. 2: Technology anarchy
- 31:18No. 3: Ticketing hell
- 40:04Takeaways
- 42:24Outro
related talks
15mPlatform Engineering - About Tools...
39mPlatform Engineering as a (Community) Service
32mHow Might You Platform: Avoiding Traps Before It's Too Late
35mPlatform Engineering Is Not About Tech
29m5 ways to screw up your DevOps Transformation
32mHow to win at platform engineering
41mPlatform Engineering for Developers, Architects & the Rest of Us
01h 25mEngineering Platforms for Engineers who Engineer Platforms