Keynote: Creating a Holistic Developer Experience
summary
Defines a concrete program: a four‑pillar framework — discoverability, usability, capabilities, stability — with specific methods (screen recordings, user interviews, search analytics, journey maps), measurable signals (onboarding time, success rate, time‑based efficiency, mean time between outages), and tools deployed (Backstage for cataloging, Helm and linters for golden paths and automation, cube flow for ML workloads, Litmus for chaos testing). A developer happiness meter 1.0 tracks real improvements as incidents get prioritized and uptime rises.
AI-written summary · about
chapters (11)
- 0:00Start
- 5:38Discoverability
- 6:18Metrics
- 6:46Centralized Support
- 6:58Backstage
- 7:30Usability
- 8:13Run Usability Testing
- 10:27Journey Mapping
- 12:03Stability
- 12:46Focus Groups
- 13:14Mean Time between Outages
related talks
16mKeynote: Does Anyone Speak Developer? Methods to Discover, Understand and Improve...
06mKeynote: Unifying Developer Experience at Zepto with Backstage: A Jo...
10mKeynote: Developer Tools - Introduction
12mKeynote: DX Is the New UX: How Technical Friction Impacts Business Value
35mBuilding Effective Developer Experience
46mForget Developer Platforms, Think Developer Productivity!
04mKeynote: 10x the Effectiveness of Dev Teams with Backstage
28mDesigning for Success: UX Principles for Internal Developer Platforms