I've been interested in this problem since like 2018. We tried to build a state machine type thing using our internal tools so that we don't have to go through the effort of like migrating to GitHub or something like that. And I think it was a valiant effort, but the code review metrics that we came up with were just never good enough to use. So my opinion kind of evolved over time because we're done. There's not just one metric that can give us an answer. Sometimes you need to look at team specific information and dicing appropriately. It's really hard to come up with a good set of metrics in an aggregate way. They can maybe catch regressions using certain things
Utsav Shah, who leads Platform at Vanta and previously led Developer Effectiveness at Dropbox, shares the story of Dropbox’s journey with measuring developer productivity. Utsav discusses what he learned about both system and survey-based measures, his opinion on the usefulness of common Git metrics, and more.