Building Effective Developer Experience
summary
Argues developer experience aims to keep people in flow state rather than just making things “easier” or “faster”, and gives concrete tactics across six adoption stages: awareness, activation, usage, learning, retention and referral. Recommends matching learning styles, anchoring to familiar CLIs or languages, using progressive disclosure, making onboarding believable (example: deliberate delay when creating a datastore), measuring with a metric like time to ship a service plus qualitative NPS, and building feedback features such as Dark’s live values and integrations with GCP and Slack.
AI-written summary · about
chapters (8)
- 0:00Start
- 9:41Awareness
- 13:03Activation
- 14:18Learning style mismatch
- 20:26Progressive Disclosure
- 22:02Error Messages & Documentation
- 23:56Customization
- 25:40Referral
related talks
26mArchitecting A Great Developer Experience
39mDeveloper Experience: How to Conquer the Hearts of Developers
18mIs DevEx not good… because we don't want it to?
27mWhat Makes a Great Developer Experience?
41mPrinciples of developer experience
27mRethinking Developer Experience
28mDesigning for Success: UX Principles for Internal Developer Platforms
07mDeveloper Experience can drive business growth