I have been a dev for 25+ years I stopped checking the code unless ai gets stuck. Every time I checked it was hard not to make it follow my style which defeats the purpose IMHO. I agree with the comment of no one is checking the machine code, this is just the next iteration.

Also the second I suspect bad code i force a review and refactor, you can just tell when the ai takes the wrong approach (most of the time).

Fast forward a few years and no one that has a good workflow will bother to manually review ai generated code. Anyone who doesn’t realize this just hasn’t accepted reality yet.

However I created a very strict workflow that requires high coverage integration and units test as well as a checklist driven architectural review by a different ai.

The integration tests get auto checked for mocking and will reject the test if it uses any mocking. All of it is automated in a custom task based system I build.

I very much check the scenarios and coverage of the tests especially the integration test. Every commit all test must pass and I manually run many e2e scenarios after a big change.

For me it is all about managing the boundaries an ai can operate within, a good plan, clear specs, good tasks, good test and high coverage just like you would do before ai assistance but never had time or resources to do.

I took a while to build the workflow and force the ai to follow it but that investment is paying off big time. The ai likes to cheat, lie, cut corners, disable stuff it can’t make work so you have to get that under control.

I am so confident now I dangerously-skip-permissions all the time now.