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

Measuring developer productivity with the DX Core 4

getdx.com

Post reply on HN
Print view View original

11–20 of 43 posts

Re: Measuring developer productivity with the DX Core 4

#11

Post by lbriner »

Developers don't like being measured for good and bad reasons. The good reason is that there is lots of effort that we expend that isn't always captured in metrics like long pieces of design or training others etc. The bad is that we don't being told that we aren't as productive as other people even if we are!

My experience is that these are only useful over a long enough period and across enough people that we can spot genuine outliers. For example, your average across the last 6 months is "15" and the average of everyone else is "25", can you help me see whether you are being given too much off-target work or are there any other issues that are blocking you getting stuff done?

Re: Measuring developer productivity with the DX Core 4

#14

Post by brabel »

stiray wrote: post #10

I would like to present DX team another metric. It is called "not wanting to work in a company that is insulting me with measures like metrics, spying on screens, squeezing every drop of sweat and exploiting its workers for already huge profit. My last job change was exactly due to company acquisition by USA company that started to exploit everything work related, removing wfh, ruining life-job ballance,... And who l…

I think metrics can be used for good. For example we are constantly try to improve our dev experience, but how do you know if you are improving anything? Developers are notably inaccurate in reporting efficiency. Unfortunately flying blind is not really an option when you need to justify paying for tools that claim to improve productivity.

Re: Measuring developer productivity with the DX Core 4

#15

Post by pipes »

lbriner wrote: post #11

Developers don't like being measured for good and bad reasons. The good reason is that there is lots of effort that we expend that isn't always captured in metrics like long pieces of design or training others etc. The bad is that we don't being told that we aren't as productive as other people even if we are! My experience is that these are only useful over a long enough period and across enough people that we can s…

Also trying to reduce productivity to some thing as silly as pull requests per hour etc ignores valuable contributions else where. Design, push back, quality, mentoring, leadership. I thought that is why meta had the "coding machine archetype" and other archetypes, recognising that just PRs aren't the only measurements.

Re: Measuring developer productivity with the DX Core 4

#17

Post by nh23423fefe »

stiray wrote: post #10

I would like to present DX team another metric. It is called "not wanting to work in a company that is insulting me with measures like metrics, spying on screens, squeezing every drop of sweat and exploiting its workers for already huge profit. My last job change was exactly due to company acquisition by USA company that started to exploit everything work related, removing wfh, ruining life-job ballance,... And who l…

[flagged]

Re: Measuring developer productivity with the DX Core 4

#19

Post by BoxOfRain »

brabel wrote: post #14
stiray wrote: post #10

I would like to present DX team another metric. It is called "not wanting to work in a company that is insulting me with measures like metrics, spying on screens, squeezing every drop of sweat and exploiting its workers for already huge profit. My last job change was exactly due to company acquisition by USA company that started to exploit everything work related, removing wfh, ruining life-job ballance,... And who l…

I think metrics can be used for good. For example we are constantly try to improve our dev experience, but how do you know if you are improving anything? Developers are notably inaccurate in reporting efficiency. Unfortunately flying blind is not really an option when you need to justify paying for tools that claim to improve productivity.

Surely no data is better than bad data? What's the point of a metric that doesn't measure anything tied to the objective reality of what it is that you're measuring?

All I see tools like this doing is getting people to manipulate the metrics, while at the same time producing enormous amounts of worker alienation. I'd even speculate the demoralising effects of workplace surveillance schemes undermine the alleged productivity benefits.

Re: Measuring developer productivity with the DX Core 4

#20

Post by Cthulhu_ »

stiray wrote: post #10

I would like to present DX team another metric. It is called "not wanting to work in a company that is insulting me with measures like metrics, spying on screens, squeezing every drop of sweat and exploiting its workers for already huge profit. My last job change was exactly due to company acquisition by USA company that started to exploit everything work related, removing wfh, ruining life-job ballance,... And who l…

My only experience with GetDX has been filling in a questionaire once a quarter that asked stuff like "how often do you go to production"; I don't know if you work in a more hostile environment, but in my case it was always used to identify points to improve, not necessarily targets.
Post reply on HN