Measuring developer productivity with the DX Core 4

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 leaves first? Those who can.

So you are not really measuring developer productivity but helping company get rid of most productive people, while all others stay.

> Whether you’re a C-level leader or a frontline manager, there is no denying that measuring developer productivity—whether to understand performance or guide improvement—is a daunting challenge.

good

Focus on the stuff that matters, not on tormenting the people that make you money.

It’s remarkable (but not reassuring) how carefully they avoid saying “part of the Atlassian family” in any promotional material for some reason.

The problem is that there are so many people involved in software development who have never developed anything but still somehow are in the position to manage others who do.

That's why there are so many stupid ideas floating around.

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?

Did anyone here ever worked under these sorts of "metrics"? I can't even imagine what a torture it would be.

the whippings will continue until Dx core 4 metrics improve

Lol, number of diffs and prs? Number of prs that focus on new features?

Those are horrible incentives.

Developers will optimize for what is measured.

How to ruin your company in 3 simple steps. Step 1: DX Core 4.

I don’t think the product is all bad; my co is using it and I feel like it is giving us some useful signals about our internal dev UX that my team can action on; we own the base level dev tooling.

>key metric >diffs per engineer