Re:What McKinsey got wrong about developer productivity
by hiAndrewQuinn on Tuesday October 24, 2023 @12:32PM
(#38001565)
Even if you couldn't measure productivity exactly, it would be astonishing if you couldn't at least slap some kind of statistical distribution shape on it based off qualitative aspects of the work. Mathematicians have done it before.
[ Parent
| on HN ]
Re:What McKinsey got wrong about developer productivity
by boxed on Tuesday October 24, 2023 @03:18PM
(#38003928)
It doesn't really work though. It's like measuring soccer based on goals or passes or some crazy shit. That's not how this works at all.
Re:What McKinsey got wrong about developer productivity
by khazhoux on Tuesday October 24, 2023 @04:24PM
(#38004956)
You’re saying there’s no conceivable way to discern which soccer players are better than others??
I don’t understand your position. Is it that all developers are equally productive, or that they do vary in productivity but it is immeasurable, an æther, with literally zero signals one could possibly mine to see how valuable a developer is to the team?
Re:What McKinsey got wrong about developer productivity
by boxed on Wednesday October 25, 2023 @04:06AM
(#38010425)
Team value is about bringing unique skills that can be a force multiplier. Measuring individual performance is antithetical to this very idea.
Soccer is a good metaphor because it's EASY to measure/see the value a good player that does not shoot a lot of goals make. In programming this is not the case.
It's certainly the case that managers that want hard numbers and don't know how to code won't be able to understand the situation at all. This is why this McKinsley nonsense is so dangerous.
Re:What McKinsey got wrong about developer productivity
by hiAndrewQuinn on Tuesday October 24, 2023 @11:07PM
(#38008703)
Or like modeling basketball games as random walks?