Data Driven DevEx at LinkedIn
summary
Tracking a commit-success metric reveals that most failures come from deprecated dependencies, so the team focuses on green builds for a slice of active Java deployables, uses ad‑hoc SQL reports then Grafana dashboards, and forces ownership via a Cruise-backed registry plus tickets that escalate to VPs. A code health policy engine enforces seven‑day fixes and escalations. Result: over 90% ticket resolution and about 95% of repositories now build at head.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 1:10Why data alone isn’t enough
- 3:37Concrete example project
- 7:46Understanding dependency issues
- 10:15Prioritizing fixes incrementally
- 13:06Creating actionable reports
- 15:55Central team intervention
- 17:41Setting policy for stability
- 19:31Automating enforcement
- 22:19Results and real outcomes
- 24:25Q&A session
related talks
28mInformation to Inspiration: Morgan Stanley's Data-Driven Approach to Developer Productivity
16mData Driven VSM for Quality Excellence
42mBuilding DevX Teams, my story
47mHow to win in software development with tighter feedback loops
33mMeasuring Developer Efficiency in DevOps: Key Questions, Metrics, Best Practices
27mDeveloper Experience: It’s Time to Start Complaining
39mDev Team Metrics that Matter
58mDeveloper Joy – How great teams get s%*t done