Whoah.
955 karma · joined September 22, 2014
Whoah.
The caveat is that it only works if you're collecting a paycheck, but not if you're bootstrapping from savings.
Similarly, the offer here is to take a deeper look at what we're building and a (quite genuine) offer to incorporate any suggestions you might have into our roadmap.
Seems like you've given this some thought on how this should be done right; would love to include them in our product development discussions.
In order to dig into enterprise data, we sort of need to have a ToS that only allows us to talking abstractly about aggregate data.
Any thoughts on how we might navigate that?
You’re right: this post is a narrative about product development, and a strong correlation we found between two variables across 20 Million+ commits that we thought was fascinating and supports general 'kitchen logic' around best practices. The axes are not labeled, but if you like we can set you up with a demo account and walk through your data with you.
One other note: the typical common use case for the product has been stakeholder management; something we have doubled down on in product development. Any specific critique about how we can improve most welcome!
Correction, the Pink title I was referring to was "Drive: The Surprising Truth About What Motivates Us"
Pink does a great job unpacking research that demonstrates how this type of 'affect my pay' dynamic backfires for engineering.
This is a big part of why we think engineering metrics are a tough nut to crack: there’s a fair bit of research that suggests tying KPIs to compensation is a huge anti-pattern for certain types of work (chiefly those involving lots of novel problem solving).
Highly recommend Daniel Pink’s “A Whole New Mind” on this topic; it’s pretty fascinating stuff.
But yeah, my co-founder has a pretty interesting take on gaming the system.
TL;DR: So, can you game the system? Absolutely. The point is to game the system: https://intercom.help/gitprime/general/cant-you-just-game-th...
^ This post scratches the surface on a timely and relevant question many teams face, but the author seems to throw hands up and say everything is subjective.
Our work suggests otherwise: https://blog.gitprime.com/check-in-frequency-and-codebase-im...