The Cohort Report allows developers to assess how their onboarding is progressing relative to past developers that joined a repo. Because of the comparative nature of the report, GitClear restricts access to individual contributors, in accordance with our policy to be the most developer-friendly analytics tool.
When viewed by an individual contributor, the report will look something like this:
A cohort is a group of people who share common characteristics within a defined period of time. It’s a great way for a new hire to get a sense for how their progress compares to others who were previously at a the same phase of onboarding.
GitClear uses cohort analysis to give developers a powerful way to understand when to seek help. Based on our experience, we’ve listed a few areas where code metrics can steer a new developer toward their path of maximum throughput and satisfaction:
Does you excel on weeks that you work on Python tasks, but struggle on weeks working in Ruby? What patterns can you find in the weeks where you're happiest, with highest Line Impact? Are there certain types of tasks that you can see a pattern of struggling with?
Are you struggling to get started? What is the state of the documentation like for a new hire? Could the environment set up process be improved for those who will later join this repo? Your cohort report will reveal whether the team needs to make an investment in upgrading the onboarding materials.
How can you challenge yourself to continue improving your efficiency, without sacrificing quality? As you continue to see your impact ascend, you can consider sharing your progress with your manager to ensure you get recognition for your arrival as a fully up-to-speed repo contributor.