What Makes a Great Developer Experience?
summary
Argues that a great developer experience targets three measurable things: cycle time, focus, and cognitive load. Shows that speeding large deliveries requires fixing tiny cycles, that observation (bad errors or unclear requirements) is usually the slowest step, and interruptions can cost ~15 minutes of recovery. Notes companies accumulate ~50 bespoke tools that can demand ~50 hours/month to learn, recommends centralizing/common CI and restricting choices (but warns against destructive mandates like forcing a single language), and urges keeping frontline engineers out of routine meetings.
AI-written summary · about
chapters (6)
- 0:00Introduction to developer experience
- 1:47Optimizing cycle time
- 8:40Improving developer focus and flow
- 14:31Reducing cognitive load
- 18:04The challenge of restricting developer choices
- 24:50Overcoming human barriers in developer experience
related talks
35mBuilding Effective Developer Experience
26mArchitecting A Great Developer Experience
10mAchieving engineering velocity by optimising developer experience
34mBuilding a Culture For Developer Productivity
27mDeveloper Experience: It’s Time to Start Complaining
07mDeveloper Experience can drive business growth
27mRethinking Developer Experience
41mPrinciples of developer experience