> "get the ick"

> even though it may work?

The first of those is about taste, and it's real, and engineers with bad taste write unstable buggy systems.

The second of those is about priority. If all you want is functional code, any old thing will do. That's what I do for one-off scripts. But if you plan to support the code at 2am when exposed to production requests on the internet, you need to understand it, which is about legibility and coherence.

I hope you do have taste, and I hope you value more than simple "it works" tests. But it might be worth looking there for why some struggle with LLM output.

For what it's worth, I use coding agents all the time, but almost never accept their output verbatim outside of boilerplate code.