[kqr]

We are definitely not. Point at a problem, and measure the cost of solving it. That's developer productivity.

We only avoid doing it at scale because it's expensive. In particular if we want the measurement to generalise out of sample.

(In particular in this case, where once we're done, proponents will claim our data is too old to be a useful guide to tomorrow.)

[xigoi]

> Point at a problem, and measure the cost of solving it.

The problem with this is that AI will create worse code that is going to cause more problems in the future, but the measurements won’t take that into account.

[kqr]

The measurements should take that into account, yes. (There are ways to estimate this.)

[Thunderer]

Measure or estimate? What ways? Honest question, because virtually all AI discussions _convieniently_ become vague a few steps short of actually answering the question.