How to win at platform engineering
summary
Argues concrete steps: get executive buy‑in, staff for customer focus and glue work, publish a team homepage with SLOs and on‑call rules, start with a pre-production pipeline then infrastructure as code (examples: hand‑rolled Windows pipelines, then IaC for k8s and VPCs), adopt policy as code (Open Policy Agent Pulumi policies terraform Sentinel) and detective controls (AWS Config rules), and prune risky homegrown systems (custom forks Atlantis with bash caused constant paging) rather than doubling down.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:12What is platform engineering
- 3:16Steps to success
- 5:00Skills for platform team
- 8:08Platform team mission
- 10:18Pre-production pipeline
- 11:00Infrastructure as code
- 12:03Policy as code
- 13:29Unloved platform adoption
- 15:58Messy infrastructure modules
- 18:46Hot potato production incidents
- 21:14Platform as 1996 I-95 tire fire
- 24:43North Star and closing
- 25:03Question and answer session
related talks
45mPlatform Engineering: A Deep Dive Conversation
41mPlatform Engineering for Developers, Architects & the Rest of Us
39mPlatform Engineering as a (Community) Service
15mThe Art of Platform Engineering
38mPlatform Engineering in the Age of AI Teammates
33mPlatform engineering: Build your own PaaS
39mThe challenges of Platform teams (and few tips & tricks...)
43m3 Ways You’re Screwing up Platform Engineering – And How to Fix It