Ask HN: How are you preventing sloppy verification with AI-assisted coding?

After the introduction of agentic code tools, the development speed has increased rapidly, but i have been struggling to keep up with the verification of these tools, since some of these things "just work"(reminds me of the old joke, "it compiles").

So i wanted to know whether this is a me problem, or others are also going through it and what your workflow for this looks like. but mostly I'm interested in the way you approach the work and the thought process behind that.

========

P.S: I'll leave the approaches i have tried before()

* always verify the work and only then approve. But this always leads me to a cognitive load and fried brain state at the end of the day. As a side effect producing poor quality work. And to resolve that i started approaching the work more slowly. This has brought down the development speed a lot but this has been good for my mental health.

* Other thing that i have been meaning to try is to get the development things done quickly, then spend another 1 or two days verifying things. This leads to continous iteration that i want and get the insights that only come after building.

* Other option i have also tried is, write tests and then refine ask it to generate code till those tests work, again the initial barrier entry becomes high, because there's so much of cases to be specified and generated and verified(this is the most reliable approach and happy path I've gotten till now that gives some sense of guarantee about whatever is built). Sometimes gain with agentic tools this initial verification has to be laid out clearly which consumes time and sometimes makes me wanna curse at AI because it misses out on somethings that i said(or i thought was clear with the spec)