Platform Engineering: A Deep Dive Conversation
summary
Argues platform engineering succeeds by changing behavior not piling on tools, using don't feed the pigeons as the rule: stop enabling brittle developer workflows. Describes converting Terraform into an inner open source layer so teams keep skills while cognitive load drops. Builds explicit OODA/UD A loops and Wardley-mapped user-anchors to make product owners into technical stewards (one org fixes a 25% mandated time bug). Recommends running small experiments (try Pulumi vs Terraform) and measuring whether loops actually speed good decisions.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:40Recap on Russ Miles' GOTOcph talk
- 5:10Platform engineering
- 15:28How to work around the product owner
- 23:40Wardley Maps
- 25:30Complexity theory
- 27:25Soft skills are hard
- 31:30Quantitative vs qualitative approaches
- 35:30Q&A
- 40:46What Russ Miles didn't know in 2014
- 44:17Outro
related talks
41mPlatform Engineering for Developers, Architects & the Rest of Us
39mPlatform Engineering as a (Community) Service
38mPlatform Engineering in the Age of AI Teammates
15mThe Art of Platform Engineering
33mPlatform engineering: Build your own PaaS
32mHow to win at platform engineering
32mPlatform Engineering Is Not About Tech
21mMake developers fly; Principles for platform engineering