Enhancing Developer Experience through InnerSource and Platform Engineering
summary
Claims $50M of code reuse from InnerSource, cites surveys that developers lose ~8 hours/week to inefficiency and that 74% of companies with DX programs see productivity gains. Presents concrete patterns: open contribution guidelines, contribution SLAs to speed reviews, documentation as code for onboarding fixes, RFCs for open design, and a blast-radius governance model that tightens rules where risk is high. Argues these change backlog dynamics, increase platform adoption, let teams add delighters, and produce more robust, higher-quality platform features.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 1:12What is developer experience
- 3:40Defining platforms and their role
- 6:52Platform backlog challenges
- 8:58Gap between platform builders and users
- 11:04InnerSource patterns for platforms
- 14:36Scalable platform governance
- 16:02Key takeaways and Q&A
related talks
21mImplementing InnerSource as Culture for Sustainable Productivity & Innovation
29mImproving Developer Experience
21mImproving your Developer Experience Through Platforms and Generative AI
14mAdopting InnerSource to maximize Developer Experience
16mEffective InnerSource Strategies for Resource-Constrained Teams
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
47mTransforming Developer Experience: A Tale of Recovery & Innovation
46mForget Developer Platforms, Think Developer Productivity!