Developer experience platforms
summary
Argues that internal developer platforms, built and run as products, cut cycle time and raise responsiveness: examples include the Financial Times doing 100+ deployments per day and teams doing 1,000 releases per week. Recommends concrete tooling and patterns: Backstage for service catalog and templates, HashiCorp Vault for secrets, Open Policy Agent for policy-as-code, npm audit to detect dependency drift (one client found 1,000+ vulnerabilities and 23 high severity). Emphasizes fitness functions, ticketless self‑service, CI into mainline, pair programming, and measured ROI (HP shifts R&D from 5% to 40% after investing ~23% in test automation).
AI-written summary · about
chapters (14)
- 0:00Introduction and context
- 1:27Business needs and IT demands
- 5:03Cloud native and microservices
- 7:29Responsiveness and cycle time
- 11:00Evolutionary architecture
- 15:54Fitness functions in practice
- 20:10Shift left security
- 22:17Agile, DevOps, and Spotify model
- 26:08Platforms as internal products
- 31:48Platform engineering teams
- 35:59Backstage and developer tools
- 40:11Fundamentals of developer experience
- 45:27Code reviews and CI/CD
- 47:31Conclusion and agility
related talks
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling
11mBuilding Scalable Developer Platforms
46mForget Developer Platforms, Think Developer Productivity!
07mDeveloper Experience can drive business growth
44mPlatform Engineering 101: Building Internal Developer Platforms
40mBuilding Developer Platforms, Birds of Feather
59mLessons from Running Developer Platforms & Communities
25mDeveloper Experience is central to DevOps success