Anirban Chatterjee argues that software teams are moving from experimenting with AI coding tools to engineering repeatable systems, but faster code generation can create verification debt when quality, security and maintainability checks do not scale with output.
He cites studies that he says found a short-lived productivity increase alongside persistent static-analysis warnings, and that people often followed confident AI advice even when it was wrong. These research claims are reported from the talk and were not independently checked against the underlying papers.
The proposed response is zero-trust, multi-layered verification. Code should be checked consistently regardless of whether a human or AI wrote it, using independent computational and reasoning-based methods with an auditable process rather than relying only on the same model or overloaded human reviewers.
The Guide, Verify, Solve loop gives agents relevant context and constraints before coding, verifies work inside the agent loop and again in the wider CI/CD process, then lets agents remediate discovered issues. Anirban Chatterjee links this approach to bounded autonomy, earlier security findings, compliance evidence and consistent standards across teams and tools.
Watch on YouTube
