Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Insights

github.com

Post reply on HN
Print view View original

31–40 of 58 posts

Re: GitHub Insights

#31

Post by [deleted] »

developer2 wrote: post #16
aupright wrote: post #7

For those worried about the data being used maliciously, it looks like most of the metrics they'll be introducing are focused around things that can actually help unblock teams and aren't focused on individual contributors. Eg. distribution of code reviews across team members for better load balancing, average code review turnaround times across the team. It also looks like you'll be able to proactively set goals for…

Nope, fuck this. The moment a product mentions "From developer to CEO" (ie. includes the word "CEO"), this is bad news. As soon as you introduce any metrics involving "participation awards" (whether based on lines of code, commits, reviews/pull-requests, etc.), the company is doomed to fail at understanding how productivity/worth is measured in the development world. The fact they even mention "CEO" in their tagline…

[deleted]

Re: GitHub Insights

#32

Post by sergioisidoro »

What is going on here? A lot of the comments on this thread seem to be confusing bad management with metric visibility. And it seems they would prefer to bury the metrics so they are not used to "snitch out" on people. Looks like a mix of dishonesty and toxic culture at work.

We basically built these metrics with Prometheus and grafana because our review queue kept growing. Now we keep everyone accountable, and make these metrics part of our stand-up meetings.

Our PR queue is now smaller, and review time is shorter. We use these metrics not to point fingers, but to ensure people are not overcommitting, overworked, and that people know how many things they have on their table.

I'm quite glad something like this is now available off the shelf

Re: GitHub Insights

#33

Post by andrewmcwatters »

aupright wrote: post #7

For those worried about the data being used maliciously, it looks like most of the metrics they'll be introducing are focused around things that can actually help unblock teams and aren't focused on individual contributors. Eg. distribution of code reviews across team members for better load balancing, average code review turnaround times across the team. It also looks like you'll be able to proactively set goals for…

I'm really happy for your sake that you've never dealt with the worst case scenario of an organization utilizing this type of product.

I also feel great pity for you knowing that you have no idea how to deal with an organization utilizing this type of product.

I hope that the industry continues to fight against these bean counter products and produce higher quality developers in the future so that we can preserve the innocence of people like you.

Re: GitHub Insights

#36

Post by dom96 »

Is this why my private repos have disabled all insights? I can't even look at pretty charts of commits I've been making anymore :(

Re: GitHub Insights

#38

Post by ryanwaggoner »

sergioisidoro wrote: post #32

What is going on here? A lot of the comments on this thread seem to be confusing bad management with metric visibility. And it seems they would prefer to bury the metrics so they are not used to "snitch out" on people. Looks like a mix of dishonesty and toxic culture at work. We basically built these metrics with Prometheus and grafana because our review queue kept growing. Now we keep everyone accountable, and make…

We use these metrics not to point fingers, but to ensure people are not overcommitting, overworked, and that people know how many things they have on their table.

Perhaps people have little faith in most management, and expect that tools like this will be used to point fingers.

You're not wrong about misuse of these tools being a symptom of bad management, but if 90% of the management in an industry is inclined to misuse such tools, it's reasonable to be dismayed when those tools are made more widely available.

Re: GitHub Insights

#39

Post by sergioisidoro »

ryanwaggoner wrote: post #38
sergioisidoro wrote: post #32

What is going on here? A lot of the comments on this thread seem to be confusing bad management with metric visibility. And it seems they would prefer to bury the metrics so they are not used to "snitch out" on people. Looks like a mix of dishonesty and toxic culture at work. We basically built these metrics with Prometheus and grafana because our review queue kept growing. Now we keep everyone accountable, and make…

We use these metrics not to point fingers, but to ensure people are not overcommitting, overworked, and that people know how many things they have on their table. Perhaps people have little faith in most management, and expect that tools like this will be used to point fingers. You're not wrong about misuse of these tools being a symptom of bad management, but if 90% of the management in an industry is inclined to mi…

You're right, it's reasonable to be dismayed, but imho not so reasonable to want to keep the metrics hidden.

Feels like we, as an industry, already had this conversation in infosec - abot security by obfuscation - which has some parallels here. The conclusion was that hiding things is generally a bad solution to the underlying problems.

Post reply on HN