Hacker News new | past | comments | ask | show | jobs | submit
We have ways to measure productivity now. AI doesn't change what to measure unless you just want to flex. Every time I see "100k lines of code, all AI," I think they probably could have done the same thing with a fraction of that. Anytime productivity is measured that way, you will always fail. As a CTO, my mantra was "I pay for outcomes, not hours." AI coding tools are just that, tools. My outlook on that hasn't changed. I enjoy working with LLM's especially locally, to handle quite a bit of the heavy lifting. I'm not paying for tokens, I'm paying for outcomes.
Which ways do we have to measure productivity for open source software? Most of the tooling around that still focus on lines of code and cyclomatic complexity