Lessons learned from 7 years of running developer platforms
summary
Seven lessons from seven years distilled into concrete practices: product-manage the platform using surveys and cycle metrics, prefer starting with one app team for 3–6 months (co-innovate and discover org quirks), run platform advocacy with developer advocates, internal roadshows and branding (yes, t-shirts), use Backstage/Cloud Native stacks above Cloud Foundry/Kubernetes, and scale by pairing and seating—move trusted engineers into new teams to spread skills and trust—avoid a 50-project rollout that never learns.
AI-written summary · about
chapters (8)
- 0:00Introduction and setup
- 1:25Seven lessons from seven years
- 7:02Defining the platform boundaries
- 12:24Treating developers as customers
- 16:38Product managing the platform
- 20:28Marketing and advocacy for platforms
- 23:38Rolling out the platform
- 28:08Closing remarks and Q&A
related talks
26mLessons Learned from 7 years of Running Developer Platforms
32mLessons Learned from 7 Years of Running Developer Platforms
59mLessons from Running Developer Platforms & Communities
33mWhy You Should Treat Your Platform as a Product
40mLessons Learned Building Developer Platforms
43mEverything You Need, Nothing You Don't: How Do You Actually Build a Lean Platform
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling
23mHow the Cloud Foundry Community Can Help Platform Engineering