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:
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.
Actionable software metrics is extremely hard to create, which is why we are often left with VERY LOW hanging fruit metrics or novelty metrics, as I like to call them. I honestly believe we are at a point now, where hardware is cheap and good enough, that we can generate very meaningful software metrics.
With GitPrime having sold for 180 USD in cash, and with GitHub and GitLab both investing in software development insights, there is a clear sign that managers and business leaders want to know what is going on. Unfortunately what we have now, in my opinion, borders on snake oil, which I'm hoping to use to my advantage to contrast my solution with others.
> Hoping you'll post a "Show HN" when you release.
Great, I'm looking forward to your upvote as getting traction is really hard :-)
