When the assistant generates code for you, how often do you stop and verify it, and what does that verification actually look like?
A strong answer gives you a real cadence for when generated code first runs, with the checks lined up from cheapest to most expensive
I try to verify as I go, I don't save it all up for one big pass at the end. Every slice the assistant generates gets a read before I move on, and I run the tests pretty often so problems show up early. If something looks wrong I'll ask the assistant to explain what it did, or just tell it to fix it. Before I call a change done I make sure the whole suite passes and I read the final diff one more time. The type checker and the linter are running the whole time anyway, so they catch the mechanical mistakes for me. My main rule is basically that unverified code shouldn't pile up. The assistant is fast, it's easy to just keep generating, so I try to keep my checking pace matched to the accept.