The Death of DevOps Has Been Greatly Exaggerated, but Platform Engineering Is Here To Stay
summary
Argues DevOps isn’t dead but a new phase is rising: platform engineering becomes the layer that abstracts infrastructure, treats developer productivity as its customer, and prioritizes cost-conscious vendor choices (pay tens of thousands to leverage millions of vendor-engineer months). Shows concrete patterns: platform teams are product teams, they run less software by creating golden paths and shared libraries, and they build internal tooling like an API for platform teams so developers self-serve rather than hand off operations.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:39True cost of software
- 3:05DevOps needs clarity
- 5:16DevOps evolution
- 7:21Operational expertise
- 9:04Platform vs infrastructure
- 10:30Infrastructure definition
- 12:12Infrastructure cost center
- 13:54Platform team leverage
- 15:21Platform organizations
- 16:45Platform team skills
- 18:11Platform vs SRE
- 19:56Developer productivity
- 21:44Automation vs infrastructure
- 22:48Self-service APIs
- 24:19Platform as product
- 25:45Cost in platform design
- 27:10Adoption challenges
- 28:13Vendor engineering
- 30:20Career paths
- 31:23Conclusion
related talks
22mDevOps vs Platform Engineering: Navigating the Path Ahead
17mDevOps Is Not Dead. Not Not by a Long Shot
49mFrom DevSecOps to Platform Engineering
41mPlatform Engineering for Developers, Architects & the Rest of Us
11mDo you really need a platform team?
56mStill Doing DEVOPS? Platform Engineering Is the Next Big Thing
38mHow to Empower your DevOps Initiatives with a PlatformOps Approach
15mThe Art of Platform Engineering