Balancing between internal and external developer experience
summary
Argument: poor developer experience burns 85 billion annual loss and teams must trade off internal speed for external simplicity. Solution examples: combine microservice endpoints behind a proxy exposure layer so external APIs present logical workflows; keep internal RAML but run a RAML→OpenAPI converter that injects code examples and rebuilds static docs automatically; accept teams using insomnia→postman bridge now and publish Postman collections later. Outcome: automated pipeline and a live developer sandbox already serve public testing.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:54Why is developer experience important
- 3:51Lack of developers
- 5:08Ease of use
- 6:54Data harmonization
- 8:56Goals
- 9:42Good developer experience
- 14:08Balancing internal and external experience
- 15:37API
- 16:15Developer experience
- 17:50Examples
- 18:12Architecture vs exposed APIs
- 20:48API management
- 21:52Documentation management
- 22:37Insomnia Postman
- 23:23Insomnia
- 25:05Outro
related talks
54mDeveloper experience platforms
07mDeveloper Experience can drive business growth
49mBuilding Software Better: API Lifecycle Management for Developers
26mArchitecting A Great Developer Experience
50mDevEx on Steroids: 5 Techniques to Scale Developer Experience
23mThe developer experience gap
17mEnhancing Developer Experience through InnerSource and Platform Engineering
28mOptimizing the developer experience through collaboration