| It's a product that I'm working on, which is focused on developer first metrics. I want to create software metrics, that developers can trust, which in turn can be used to properly gauge productivity and risk. I've studied software metrics for quite sometime and they are widely despised by developers, because they are a) not useful for developers b) never put effort into context that can be discussed, vetted and refined. What I'm trying to do is fix the stigma associated with software metrics, by focusing on how they can be used by developers. For example, code churn metrics can be used in a positive way for developers as the following example shows: https://imgur.com/OMD8rFF Without looking a single line of code, you can estimate the impact each commit will have, which can be useful for domain experts, team leaders, etc. I'm hoping to have a version of the product that people can install via docker or on bare metal linux by the end of this month. |
Good points about software metrics. I'm not a big believer in them, either. I think the most useful metric I've ever needed or been able to use was in one case where I needed to see a developer's contribution activity. Looking at a specific developer, aggregated across a Github organization, it was clear they were just not doing much work!
Hoping you'll post a "Show HN" when you release.