Earlier quoted context omitted.
No, it's because reading code is slower than writing it. The only way these tools can possibly be faster for non-trivial work is if you don't give a shit enough about the output to not even read it. And if you can do that and still achieve your goal, chances are your goal wasn't that difficult to begin with. That's why we're now consistently measuring individuals to be slower using these tools even though many of the…
"Consistently"? Is there more than just the one METR study that's saying this?
The tools are absolutely useful, but they need to be applied in the right places and they are decided not a silver bullet or general-purpose software engineering tool in the manner that they're being billed at present. We still use them despite our finding, but we use them judiciously and where they actually help.