Guide, Verify, Solve — Anirban Chatterjee, Sonar

Code checks can inform an agent while it is writing, before a change reaches formal review. In Sonar's proposed development workflow, the agent receives coding constraints, generates changes, asks verification tools for identified issues and fixes those issues before continuing.

The presentation also retains a separate review stage for the complete proposed change, which can block it before it proceeds. The two checkpoints serve different purposes: immediate feedback helps prevent an identified mistake from spreading through further generated code, while the later gate evaluates the accumulated change. Sonar presents this as a verification design, without demonstrating that it detects every possible defect.

“while participants did follow the AI advice 92.7% of the time when the AI was correct, they unfortunately also listened to the AI nearly 80% of the time when the AI was wrong”

Anirban Chatterjee

“And so there's a lot of rubber stamping that I'm sure is happening in all of your organizations. It's happening everywhere.”

Anirban Chatterjee

“software is not provable in the same way that code is provable. Software can break in interesting and novel ways”

Anirban Chatterjee

“there was, in fact, a temporary spike in productivity, um but it lasted about 3 months and then it went back down”

Anirban Chatterjee

“None of these models are ever going to be perfect. You're always going to have some kind of need for verification in the loop”

Anirban Chatterjee