The developer experience gap
summary
Argues that a persistent developer experience gap comes from an abundance of cloud primitives (s3, ec2, managed services) that developers must assemble and operate themselves, creating low-level friction; cites heroku as an example of an integrated experience and notes a surprising resurgence of interest over the last 18 months. Recommends solutions that are comprehensive, developer native (integrated into tools like visual studio code and marp), elegant, multi-runtime, and require vendor collaboration rather than siloed APIs.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:45The Developer Experience Gap
- 5:31Heroku
- 8:35A Golden Age for Developers
- 8:57Progressive Delivery
- 13:51Eliminate Friction
- 20:25Redmond Programming Language Rankings
related talks
25mDeveloper Experience is central to DevOps success
07mDeveloper Experience can drive business growth
35mBuilding Effective Developer Experience
28mUnleashing Innovation by Unblocking your Developers
46mForget Developer Platforms, Think Developer Productivity!
27mWhat Makes a Great Developer Experience?
39mDeveloper Experience: How to Conquer the Hearts of Developers
54mDeveloper experience platforms