How Might You Platform: Avoiding Traps Before It's Too Late
summary
Covers a platform team’s migration from VMs to Kubernetes, the failed custom extension of Envoy XDS that became tech debt, and the later switch to Istio, Helm charts and CRDs. Describes building internal logging to cut vendor cost ~50%, creating golden paths and standardized templates, and adding observability and a deployment preview to reduce risky manual deploys. Emphasizes product management, stakeholder buy‑in, measurable metrics and when to reuse community tools versus owning everything. Useful if you want concrete pitfalls and remediation steps.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:02Why platforms emerged
- 7:23From firefighting to platforms
- 10:15Platforms for scalability
- 13:28User-centric platform building
- 16:20Platform product management
- 18:30Stakeholder collaboration
- 22:01Avoiding distractions
- 24:50Custom vs vendor tools
- 26:37UX research for platforms
- 28:50Engineer confidence
- 30:18Platform practices
related talks
43m3 Ways You’re Screwing up Platform Engineering – And How to Fix It
33mWhy You Should Treat Your Platform as a Product
39mPlatform Engineering as a (Community) Service
31mPanel Discussion: Platform and Developer Productivity - Trends and Challenges
12mUnveiling the Future: Navigating Cloud Strategy, Platform Engineering, and Architectural Evolution
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling
50mWhy is it so Hard to Create a Great Platform-as-a-product?
25mWho Built This Platform? Alternative Viewpoints on Platform Design - Diana Todea & Elif Samedin