An Open Source Approach to Driving Developer Efficiency
Talkat Open Source in Finance Forum New York 2022 · on Thursday, 2022-12-08· at 16:15· HUB 3, New York, NY, USA·
summary
Company open-core instances send heartbeat data to GitLab and the talk shows concrete metrics: onboarding often takes six months to a year (~$50k per hire), context switching and self‑interruptions cause large delays, and a single rock‑star developer doing 100 commits a day can skew team metrics. Time‑blocking (no meetings 10–3) doubles bug closure velocity. Recommendations include surfacing CI/CD signals in a single place like the merge request widget, mining automated data before manual, and using studies (multi‑university, pair‑programming) to redesign teams.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:43Developer Efficiency
- 10:34Impacts of Context Switching
- 34:28Merge Request Widget
- 36:55Measuring Developer Productivity
related talks
34mBuilding a Culture For Developer Productivity
47mHow to win in software development with tighter feedback loops
40mGamifying Dev Effectiveness in a Remote-first Work Environment
10mAchieving engineering velocity by optimising developer experience
27mWhat Makes a Great Developer Experience?
24mRemote development can improve your developers remote work experience
31mDeveloper productivity is waste
52mConfronting Common Productivity Hurdles in Modern Software Development