You are trying to justify blaming the tool, not how it is used.

Do you also blame a screwdriver for not being able to hammer nails into the wall? Learn the tool and how to use it, decide where it makes sense. Like you should do with all tools.

> The hardness/loop thins it's just yet another pattern invention to justify agentic coding.

In my case, building my harness has sped up reverse engineering immensely. An agent can debug kernels, UART, I2C busses, firmware blobs, binaries within minutes what otherwise would have taken me weeks if not months. And that's just because I gave it a workflow to do this, with build/debugging containers, and the possibility to write Go libraries and bindings in an isolated manner.

They are really good at doing the gruntwork, if you build a testable workflow for them. The TDD/unit/end-to-end tests turn plausible code into deterministic code, and that's the core difference in usage.

> Btw many of us still hand code, not just reading it, for assuring and be actually accountable for what we release.

I also never said that I am not proofreading and refactoring everything they generate, that's your assumption.