Platform Engineering Is Not About Tech
summary
Argues that platform engineering success depends more on organizational change than on technology: despite tools like GitLab, Argo, Flux, Kubernetes and vendors such as Mia-Platform, about 70% of platforms fail and ~80% of organizations plan platform teams. Describes common practice of building internal developer portals and automation (one example scaled to ~100 people) and points out adoption failures caused by lack of product thinking, branding, ambassadors, metrics, governance, clear MVP scope and plans for sustainable maintenance.
AI-written summary · about
chapters (9)
- 0:00Platform Engineering provocation
- 3:37True goal of Platform Engineering
- 7:27Tech and org linkage
- 10:01Common platform mistakes
- 13:55Internal product platform
- 17:45Sustainable platform strategies
- 22:20MVP and long-term vision
- 25:09Final takeaways
- 26:11Q&A
related talks
20mPlatform Engineering Is Not About Tech
35mPlatform Engineering Is Not About Tech
44mPlatform Engineering is All About Product
39mPlatform Engineering as a (Community) Service
19mPlatform Engineering beyond the Buzzword?
33mThe Platform Engineering Journey
29mKeynote: Building Bridges with Platforms: The Role of the Platform Engineer
15mPlatform Engineering - About Tools...