When the Green Check Proves the Wrong Thing
The risk is not generated code. It is confidence without evidence. AI can help a software team produce a plausible first draft faster. Approval still depends on evidence. A pull request that reads well, passes continuous integration and arrives with tests can still fail to show that the risky behaviour is safe. Near the end of the day, a small pull request lands in the review queue. It changes retry behaviour around an external payment provider. The changed lines are easy to read. CI has passed. The summary says the change improves resilience when the provider is temporarily unavailable. A few unit tests simulate a failed call, then a successful one. The retry code runs. The code follows a familiar pattern. Nothing looks careless. There is plenty for a reviewer to accept. The code is…