Lessons Learned from 7 years of Running Developer Platforms
summary
Seven years of running internal developer platforms yields concrete lessons: Kubernetes adoption often reduces release velocity once you scale, so platform teams focus on automating the build and CI/CD pipeline (many orgs still lack full CI/CD). Successful platforms treat developers as product customers, run a developer-toil survey every few months to track improvements, start by onboarding one real application to prove value, then scale — banks report platforms supporting ~1500 applications globally.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:37What is a developer platform
- 9:10Platform teams vs developers
- 12:39Treating developers as customers
- 17:34Automating the build pipeline
- 18:15Developer toil surveys
- 22:58Rolling out the platform
related talks
32mLessons Learned from 7 Years of Running Developer Platforms
59mLessons from Running Developer Platforms & Communities
33mLessons learned from 7 years of running developer platforms
40mLessons Learned Building Developer Platforms
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling
33mWhy You Should Treat Your Platform as a Product
30mPlatform as a Product
35mPanel: Navigating the Path to Platform Engineering...