Contribution analysis for your Dev Team — Hezheng Yin // Merico
- Part 1Managing international engineering teams — Hezheng Yin // Merico
- Part 2 Contribution analysis for your Dev Team — Hezheng Yin // Merico
Show Notes
-
02:11The inspiration behind developer product contribution analysisIt was to solve the open-source funding and distribution problem. The idea was to have an algorithm that looks into your Git repository and all the relevant data and then decides how much relative contribution each developer makes to the project.
-
04:17How the developer contribution algorithm workedIt was initially the number of lines, but there was a need to assess the relative importance of different functions in the codebase. So, it uses the function called the relationship between functions.to construct the call graph of your code base.
-
06:55Why is measuring developer contribution to product important?Intellectual shareholding. The end goal is to make every developer a shareholder of the open-source project they're working on by contributing intellectually.
-
12:57The value of metrics in the industryThe value of metrics comes down to how we measure anything we're doing here, right, how much value they're delivering, and how much impact they have.
-
16:11What impact does it have on developers when they know the CTO has insight and visibility into various metrics?The process becomes more efficient, and many developers use these metrics to drive their agenda forward.
Quotes
-
"Back then, when we started. It's just the lines of code or the number of commits; these are the metrics that GitHub insights display to developers. We thought we needed to look deeper into the code when we started working on this problem. We needed to understand better the relative importance of different pieces of code. And so that's why we started looking into an algorithm similar to PageRank. We use that idea to determine the relative importance of different functions in your codebase" - Hezheng Yin
-
"Intellectual shareholding. The end goal is to make every developer a shareholder of the open-source project they're working on by contributing intellectually." - Hezheng Yin
-
"Our algorithm works by assigning a value to each commit. So that value you can think of as the credit you know, contributed, assigned to that commit. And every commit is associated with its author. So, if you run the algorithm, we can see how much each author has contributed to the project." - Hezheng Yin
-
"The value of metrics comes down to how we measure anything we're doing here, right, how much value they're delivering, and how much impact they have." - Hezheng Yin
-
"Let's imagine next week, one of your door metrics was cut in half or doubled. How would you figure out what's happening? What's the root cause of it? Then you need to look at more granular metrics, like your PR cycle time, right? Like if your dollar metric change, lead time gets doubled? It could be because your PR pickup time gets doubled. And that's causing, you know, you need to be faster in delivering new features to your customers." - Hezheng Yin
-
"We have a range of feature errors that can support the debugging of DORA features. And you look at them when something goes wrong." - Hezheng Yin
-
"Many of our users find their process more efficient because everyone speaks the same language. Now, they're all aligned on things that they think are important because otherwise, they might be working on something that their manager or their director, you know, might not value that much. Now there's a common goal they can work towards together." - Hezheng Yin
- Part 1Managing international engineering teams — Hezheng Yin // Merico
- Part 2 Contribution analysis for your Dev Team — Hezheng Yin // Merico
Up Next:
-
Part 1Managing international engineering teams — Hezheng Yin // Merico
Leveraging global engineering talent is increasingly impossible to pass off. But how do you manage such a team with diverse cultural backgrounds? How do you ensure everyone is in sync when a scrum is impossible to schedule? And how do you foster collaboration among teams to move your company forward? Tune in to this episode of the CTO Podcast as Hezheng Yin, Cofounder & CTO at Merico, discusses strategies to manage international engineering teams.
Play Podcast -
Part 2Contribution analysis for your Dev Team — Hezheng Yin // Merico
Development is a continuum, with team after team continuing to improve the code base. How do you handle inherited code base and technical debt? How does a new team measure and value its contribution to the product against the inherited code base? Listen to this episode of the CTO Podcast as Hezheng Yin, Cofounder & CTO at Merico, discusses contribution analysis for dev teams.