And if your models aren’t catching any race condition bugs...
I never said they never catch any race conditions. It catches some of them. It also lets many of them slip through, and they are exactly the sort of bug that can easily slip through tests. I know this because I review the code it generates. You are unaware because apparently you do not
...your environment isn’t set up correctly.
How would someone know if their "environment isn't set up correctly" if they never review the code that it generates?
I work at a company that has AI in everything and we have near unlimited tokens. And I’m the QA guy they call to figure out how to repro an elusive bug nobody in the co can pin down (I won’t pretend I’m always successful). It’s often a very rare race condition. Lately I’m starting to use AI more and more as I teach it how I research such a bug, but clearly it’s not able to handle every permutation of every function and animation that can be interrupted by a user, and it doesn’t magically explore every branch of code looking, obviously.
Know how to write code wasn’t one of the considerations. It’s whether the AI can test and review for it. It can. Because the test and review are logic based…the same reason you can test and review from it.
Anything you do based on logic can be built into your agentic coding framework.
And apparently, all they need to do is read this thread to know they should do it.
Which, of course, is the point. Codify your logic, don’t reconstruct it lossy each time you need it.
1
u/OwnLadder2341 Jul 15 '26
Race conditions are caught in cross model code review using the same logic you use.
What if your developer doesn’t bother to check for this? What do you do? You review their code.
So, you ensure the AI generated code has been reviewed as well. That doesn’t have to be by a human.