@davidsonsr @barubary @EUCommission
Developers aren't being evaluated by or paid for KLOCs anymore, so it's not invalid to view an increase in code throughput as an indicator of increased productivity during experimental evaluations
What? Developers aren't paid for pissing on the floor, therefore it's not invalid to view an increase in the amount of piss on the floor as an indicator of increased productivity during experimental evaluations.
That made exactly as much sense as what you said.
You are completely ignoring the reason why developers are not paid per line of code anymore: because it does not correlate with useful productivity.
New code added is technical debt. The ideal change set is one that reduces the total amount of code and does not harm functionality. The very best changes I've reviewed are ones that simplify the code and simultaneously improve performance.
It's very easy to add code more quickly. If I wanted to, I could easily increase my productivity measured in lines of code changed by a large factor, simply by copying and pasting more code instead of building clean abstractions, but throwing in buggy implementations rather than thinking through the corner cases, and so on. And LLMs make it very easy to do all of these things. That's not productivity, that's just creating future problems (and, potentially, liability if you're in an industry where you can't just disclaim all liability, such as, oh, I don't know, The EU, where the CRA explicitly prohibits this).