Find friction in your developer experience by user testing with developers
summary
Recommends running a simple DX test with five developers (captures ~80% of issues) over one hour, recruiting via a screener and paying $50 Amazon gift cards, recording moderated sessions with Zoom or unmoderated screencasts with OBS. Finds surprising blockers like five‑out‑of‑five users failing to sign up because adblock blocks a redirect and hidden free‑tier limits that return a 403 after five sends. Proposes concrete fixes: raise limits, surface clear error messages, and add docs notices.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:30Who am I?
- 0:51What is Haxor?
- 1:20What DX testing looks like.
- 2:32Why developer experience testing?
- 3:28How to conduct a
- 11:08Define the test script.
- 19:123. Administer the test.
- 20:42Review the results.
related talks
24mUsability Testing for Developers
25mThe hacker's guide to usability testing
31mEnhance Developer Experience by community
26mEnhance Developer Experience by community
29mBuilding What Developers Actually Want: Lessons Learned
53mLet's talk about DX, Baby!
32mScaling Developer Experience at Reddit, Airbnb and Amplitude
47mTransforming Developer Experience: A Tale of Recovery & Innovation