From Developer Experience to Business Value
summary
Capital One’s Android teams describe DevX around a 6–7 realistic score after creating a platform team that developers say improves timelines and stability; clean build times moved from minutes to ~30 seconds in one comparison. Measurement comes from DX surveys twice a year plus gradle build/configuration times, dependency download and CI wall time. Built tools include an in‑house multi‑repo app builder, SOMO and DX toolbox for onboarding, KSP to cut boilerplate, Bitrise and Claude for async work. Problems: flaky UI tests (200 tests rerun on retry), and a proposed prompt-based UI test generator that a dev estimates could speed testing ~10x. Mentioned vendors include Flank for Firebase Test Lab and Gradle Enterprise.
AI-written summary · about
chapters (10)
- 0:00Developer experience intro
- 1:02Current DX scores
- 2:46DX score factors
- 8:46AI for dev & testing
- 14:02Positive contributions to developer experience
- 18:38Measuring DX impact
- 20:26Consistent DX patterns
- 22:11Tooling improves workflows
- 25:48Onboarding automation
- 32:58Getting DX buy-in
related talks
22mDX for Internal Teams
27mDeveloper Experience: It’s Time to Start Complaining
44mDefining “DevExT”, the Developer Experience in Testing
32mScaling Developer Experience at Reddit, Airbnb and Amplitude
47mDesigning the Developer Experience
37mBecoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and Gradle
36mDeveloper Productivity Engineering: What's in it for me?
20mEmpowering Developers: Driving Innovation for the Future of Work TechLead