6 ms·
> As an experiment we’ve starred building an app that measures things like PRs and commits for each developer. Ever heard of perverse incentives? This repeats
by breckenedge 5y ago
> As an experiment we’ve starred building an app that measures things like PRs and commits for each developer.
Ever heard of perverse incentives? This repeats errors made in the early 80s.
- jstx1 5y agoGoodhart's law - https://en.wikipedia.org/wiki/Goodhart%27s_law https://en.wikipedia.org/wiki/Goodhart%27s_law > When a measure becomes a target, it ceases to be a good measure.
- high_byte 5y agoI'm gonna live by that from now on.
- quickthrower2 5y agoThen make an OKR that you’ll say it to yourself everyday for 91 days.
- auslegung 5y agoThis 100%. Also, to the OP, what goal do you want the engineers to achieve? More lines of code? That means more bugs and sometimes it means a worse implementation. More PRs? Well that’s just dumb. You want engineers to solve business problems. Sometimes that involves code, sometimes it doesn’t. Can you quantify and qualify “solutions to business problems”? Do you want solutions that bring in thousands of dollars or millions? Over what time? Requiring how many resources to achieve? Etc etc. I hope I don’t sound hostile, it’s just that, when done poorly, the kinds of solutions you mentioned can literally bankrupt a business. It also shows a gross misunderstanding of how incentives work, and what you’re wanting to achieve.