Engineering Experience
summary
A concrete claim: embed UX into development by running pair designing sessions and compiling diagnostic user profiles (device CPU/RAM, battery, network availability, times of use). A refactor of a mobile social app reveals bugs that only appear during power outages and intermittent Wi‑Fi; adding explicit offline/error handling and testing on low‑spec devices eliminates weeks of post‑release fixes. Result: fewer cosmetic and runtime bug reports, shorter delivery cycles, reclaimed time for learning, and happier clients.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:51Technology is everywhere
- 14:03Let me tell you a story...
- 21:23How we solved this?
- 27:59Questions?
related talks
27mDeveloper Experience: It’s Time to Start Complaining
11mWorking with sharp tools - A case study of Continuous deployment
36m"Engineering to embrace change" Or "How clumsy engineering can lead to powerful research – Part II"
24mOvercoming Resistance: UX Practices in Agile Teams
43mLessons from Mobile
19mDon't Build to Last: Strategies for Designing and Productionising Experiments
57mCoffee-break with EngX Experts
27mDebugging product engineering organizations