Comment by walt_grata
Comment by walt_grata 12 hours ago
Fuck is there a way to have that degree and not be clueless and toxic to your colleagues and users.
Comment by walt_grata 12 hours ago
Fuck is there a way to have that degree and not be clueless and toxic to your colleagues and users.
Yes, the problem of accurately measuring software "productivity" has stymied the entire industry for decades, but people keep trying. It's conceivable that you might be able to get some sort of more-usable metric out of some systematized AI analysis of code changes, which would be pretty ironic.
They seem better at working in finance and managing money.
Most models of productivity look like factories with inputs, outputs, and processes. This is just not how engineering or craftsmanship happen.
It's because the purpose of engineering is to engineer a solution. Their purpose is to create profit, engineering gets in the way.
It all comes from "if you can't measure it you can't improve it". The job of management is to improve things, and that means they need to measure it and in turn look for measures. When working on an assembly line there are lots of things to measure and improve, and improving many of those things have shown great value.
They want to expand that value into engineering and so are looking for something they can measure. I haven't seen anyone answer what can be measured to make a useful improvement though. I have a good "feeling" that some people I work with are better than others, but most are not so bad that we should fire them - but I don't know how to put that into something objective.