Designing the Developer Experience
summary
Built a cloud infra platform and an IoT platform that cut a critical hardware test cycle from two–three weeks to two–six hours by enabling remote test‑bench updates and automated tests, and replaces week‑long resource requests with self‑service scaling via PRs. Tooling includes a CLI with built‑in help, progress indicators and color, plus personas, developer journeys and user stories that capture the why, a baseline NPS survey for metrics, and a community hackathon that fed real extensions back into the platform.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:59Meet Jacob
- 1:47What is a developer experience
- 2:49Benefits for the business
- 3:43Personas
- 5:41Biggest pain points
- 7:04Developer journey
- 10:22Different user interfaces
- 11:37CLI example
- 13:49Challenges
- 15:04Survey
- 16:39Technical Concept
- 19:54User Stories
- 23:35Building Relationships
- 26:10Measuring Developer Experience
- 29:58Why invest in a good Developer Experience
- 30:45The biggest pain points for developers
- 34:03Speed
- 36:56What do developers look for
- 39:03Investing in developer experience
- 41:03Questions
related talks
54mDeveloper experience platforms
29mImproving Developer Experience
46mForget Developer Platforms, Think Developer Productivity!
11mBuilding Scalable Developer Platforms
07mDeveloper Experience can drive business growth
46mWork It Smarter, Dev It Better, Ship It Faster, Test It Stronger
02h 31mDeveloper Productivity Engineering - Extended Session
36mDeveloper Experience : From Hype to Reality