upvote
Speed is only one factor, quality should matter.
reply
How can you measure quality without time boxing, and therefore measuring speed?
reply
Quality is orthogonal to time taken although likely correlates positively.

Michelangelo's David took years to complete, many studies and iterations. The patrons that paid for it wanted the perfection such an artist could provide - that was not something to be rushed.

Software that is ergonomic, intuitive, fast, and maintainable takes time. To use the analogy - chipping away at granite is a slow and tedious process, mistakes in planning or approach are difficult if not impossible to recover from.

Taking time to do it right sometimes is the only way to achieve quality.

reply
The contest doesn't make sense. 1 hour with access to AI is clearly going have an advantage over 1 hour without - nobody claimed otherwise.

The problem is that, in the real world, people are neither competing for maximizing the code quality score, nor are they spending remotely the same amount of time with vs. without AI. They're spending a small fraction of the time with AI than they otherwise would have, and their goal is to ship the product. Hence why they commit bad code.

To put it bluntly, I've literally seen engineers who used to send excellent pre-AI code suddenly start sending trash for review when they use AI. And, when I push back and point out the problems and they actually put in the effort to improve it, their code quality improves to (or beyond) what they (or I, for that matter) would've written without AI. I don't know how you could get a more fair experiment than this.

So, to answer your question directly, no. (No for other reasons too, but this is the only relevant one.)

reply