(I'm an engineer at Sourcegraph, but otherwise share your healthy skepticism of companies in general)
For what it's worth, I don't think that's accurate. I've worked closely with the team that builds Code Insights, and at pretty much every point they've been vehemently opposed to exposing any metrics that could ever be used to track/monitor devs.
On the contrary I've actually heard most use cases of it in companies are actually devs themselves showing leadership/management clear graphs of "look, code quality here is getting worse, we need more time in sprints to improve this"
Anyway, just my take, not commenting in any official capacity.
Blend that in with some product intelligence to manage stackholders and booya, a solid nice product/dev integration.
Quality of user stories and product cycle would be interesting to see as it has a direct impact on dev quality (ie how much do they have to guess versus cleanly mapped out).
It's pretty cool and I see where you are going with it.
For what it's worth, I don't think that's accurate. I've worked closely with the team that builds Code Insights, and at pretty much every point they've been vehemently opposed to exposing any metrics that could ever be used to track/monitor devs.
On the contrary I've actually heard most use cases of it in companies are actually devs themselves showing leadership/management clear graphs of "look, code quality here is getting worse, we need more time in sprints to improve this"
Anyway, just my take, not commenting in any official capacity.