You Keep Using That Word 'DevEx' - I Do Not Think It Means What You Think It Means
Talkat Platform Engineering Day North America 2025 · on Monday, 2025-11-10· at 16:30· Building B | Level 5 | Thomas Murphy Ballroom 2-3·
summary
Platform teams focus on infra but adoption stalls because developers need local cloud API access and language-native SDKs, test data management, and automated test environments rather than just faster CI/CD or another Kubernetes hammer. Measure impact — one API with 10,000 calls/day and a single client is less critical than one with 5,000 calls/day and five clients, so measure active registered clients and mean calls per client. Improve dev workflows by shadowing or onboarding onto product teams, hiring versatile “Swiss‑knife” engineers, and treating tools as capabilities not trophies.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:46Why DevEx matters
- 3:36Developer workflows and needs
- 7:55Measuring DevEx impact
- 10:47Team for DevEx
- 13:18DevEx traps
- 15:47Defining DevEx strategies
- 16:51Improving DevEx steps
- 18:16Q&A
related talks
55mDemystifying “DevEx” and Why It Matters
50mDevEx on Steroids: 5 Techniques to Scale Developer Experience
24mDevEx on Steroids: 🚀 5 Hacks to SUPERCHARGE Developer Experience
41mThe New DevEx Landscape: Thriving with AI and Automation
38mHow to Build Better Developer Platforms
53mWhere devs are challenged, what devs want and where DevEx is going
46mForget Developer Platforms, Think Developer Productivity!
29mImproving Developer Experience