Lessons Learned from 7 Years of Running Developer Platforms
summary
Seven years running a developer platform yields concrete moves: hire product and UX roles, run a value stream map to cut handoffs, ship a pre-integrated platform and then customize, and embed rotating on-call advocates with ticketless Slack support. Outcome: one rollout reaches 4,000 engineers with nearly 100% adoption in 12–16 months by promoting a single golden path and measuring deployment frequency, while emphasizing org, controls and retraining over DIY wiring.
AI-written summary · about
chapters (13)
- 0:00Intro
- 3:02Value of Developer Experience
- 6:14Eternal Recurrence (platform, PaaS, DevOps, etc)
- 8:58Product Mindset
- 12:04Learning - Devs Are Your Users & Customers
- 16:10Research Interview Example
- 16:44Golden Path & Platform Dependencies
- 17:07Branding, Marketing & Training
- 20:11Measuring the Right Things
- 22:13Start With Integrated Solution & Customize
- 23:26#5 Start With Integrated Solution & Cu
- 26:25Getting Started - Create Platform w/ Devs
- 28:05Scaling - Pair and pollinate seeds 1. Brand & market platform
related talks
26mLessons Learned from 7 years of Running Developer Platforms
33mLessons learned from 7 years of running developer platforms
59mLessons from Running Developer Platforms & Communities
40mInternal platforms in practice
43mEngineering Platforms Evolved
33mWhy You Should Treat Your Platform as a Product
54mDeveloper experience platforms
40mLessons Learned Building Developer Platforms