Industry Executive Panel featuring
summary
Panel argues the real problem is rising complexity and tool sprawl — too much YAML, too many homegrown Heroku-like platforms, and a widening gap between devs and customers. Concrete fixes include decoupling workflow change from tooling (migrate teams to Kubernetes only after process shifts), measuring deploy frequency and mean time to recovery tied to business outcomes, and treating a customer story as user story cycle time. Expect more vertical cloud-native stacks and shared internal platforms.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:21Jason Warner
- 2:41General Manager of the Cloud Native Computing Foundation
- 21:10Should every Business Write Their Own Database
- 34:48Stakeholder Alignment
related talks
46mPanel Discussion: The number of orche
39mPlatform Engineering as a (Community) Service
36mPanel Discussion: Leveraging Cloud Native Technology to Transform Your Enterprise
29mThe Platform Engineering Revolution Panel: Empowering Developers Through Self-Service
41mKeynote Panel - End User Council - Moderated by John Mark Walker
33mPanel: Composable Platforms in the Real World: What Works, and What Really Doesn't
41mPlatform Engineering for Developers, Architects & the Rest of Us
35mHow to Cloud Ops Like a Boss
