Rethinking Developer Experience
summary
Defines developer experience as the practices and tools that let teams deliver great end‑user UX, backed by Microsoft’s Developer Velocity Lab and a six‑year DORA metrics study (deployment frequency, lead time, change failure rate, time to restore). Recommends measuring stability and throughput per Modern Software Engineering, tightening feedback loops to seconds, and choosing intentional dependencies (stable semver, clear provenance, license, docs, humane support). Operational advice: use one package manager, run security scans, vendor when needed, and practice infrastructure as code.
AI-written summary · about
chapters (10)
- 0:00Introduction to DX
- 1:27Defining developer experience
- 3:11What DX is not
- 8:29DX logical fallacies
- 12:47DX beyond happiness
- 15:14Strategy and tactics for DX
- 16:40Modern software engineering
- 19:30Intentional dependency selection
- 23:44Managing infrastructure as code
- 25:07DX as a continuous journey
related talks
25mDeveloper Experience is central to DevOps success
26mArchitecting A Great Developer Experience
39mDeveloper Experience: How to Conquer the Hearts of Developers
07mDeveloper Experience can drive business growth
41mPrinciples of developer experience
35mBuilding Effective Developer Experience
10mAchieving engineering velocity by optimising developer experience
27mWhat Makes a Great Developer Experience?
