Nuances of Influencing Developer Experience and Productivity Through Tech Products
summary
Panelists consolidate 80+ years of experience to report concrete changes: adoption of DORA metrics and OKRs, building telemetry built into features to measure outcomes not just lines of code, and rolling out CI/CD and shift-left testing with Spinnaker-style pipelines. Claims: telemetry and dashboards move adoption when champion teams prove value; POCs often never reach production due to resources and cross-dependencies; Quiet AI (formerly ShiftLeft), DeployHub-style tooling, Git/LFX data and GitHub Copilot are highlighted as practical levers.
AI-written summary · about
chapters (8)
- 0:00Developer productivity intro
- 2:10Panelist backgrounds
- 7:03Measuring productivity impact
- 16:32Adopting productivity metrics
- 23:15Open source vs enterprise cultures
- 28:12Barriers to new tech adoption
- 31:17Future of productivity
- 35:54Q&A on metrics
related talks
35mPanel: Developer Experience and Productivity
34mBuilding a Culture For Developer Productivity
43mMeasuring Developer Productivity: The Good, the Bad and the Data
31mPanel Discussion: Platform and Developer Productivity - Trends and Challenges
24mBeyond the Commit: A Fireside Chat on AI and Developer Productivity
18mFrom developer productivity to engineering impact
28m05 how we do developer productivity panel
31mDeveloper productivity is waste