---
title: "Guide, Verify, Solve: The Engineering Discipline Agentic Development Demands"
category: "talks"
date: "2026-07-01"
time: "11:40am-12:00pm"
track: "Agentic Engineering"
room: "Track 8"
speakers: ["Anirban Chatterjee"]
sourceLabels: ["Official conference schedule", "Public YouTube metadata"]
scheduleTrack: "Agentic Engineering"
scheduleRoom: "Track 8"
scheduleLabels: ["Agentic Engineering", "Track 8", "session", "confirmed"]
---
# Guide, Verify, Solve: The Engineering Discipline Agentic Development Demands

## Conference Context
- Date/time: 2026-07-01 · 11:40am-12:00pm
- Track/room: Agentic Engineering · Track 8
- Speaker(s): Anirban Chatterjee
- Session type/status: session · confirmed

- Track: Agentic Engineering
- Room: Track 8
- Session type: session
- Status: confirmed

## Session Description
Agentic development is not a productivity story: it's a reliability engineering problem at a scale most teams have never faced. Long-running agent tasks fail at alarming rates, pull requests have grown from 50 lines to 5,000, and cognitive surrender is real—the more capable AI output appears, the less humans interrogate it, right at the moment the stakes are highest. Independent, peer-reviewed research from Carnegie Mellon studying 807 open source projects found that AI agent adoption caused a persistent 30% increase in code analysis warnings and a 41% increase in complexity — with long-term development velocity declining as a result. Agents don't just write code faster, they accumulate debt faster, too. The answer is not to slow agents down, it's to govern and refine the loop they operate inside. Sonar's Agent Centric Development Cycle (AC/DC), defines that loop across three continuous stages: guide agents with project-specific context and constraints before a single line is written; verify rigorously and continuously inside the loop, not downstream in CI; and solve issues automatically before they ever reach a manual review. The deeper insight is that this is not primarily a security story. It's an efficiency story. Codebases riddled with complexity make agents slower, less reliable, and significantly more expensive to run. Every token spent navigating legacy debt is a tax on every future agent run. Well-maintained, low-complexity codebases mean fewer failures, fewer tokens, and faster iteration. The teams that instrument this loop now will do more than ship safely: they'll compound their advantage every time an agent touches their codebase. Verification isn't a cost center. In an agentic world, it's a competitive moat.

## Media Evidence
No related AI Engineer channel video found yet.

## Evidence Graph
This evidence graph is generated from currently linked source material: official schedule text, related video pages, cached transcripts, visible slide text, dense/reconstructed slide pages, and AI slide-classification audits.

### Media Signals
No linked video, transcript, or slide source has been attached yet.

### Agent Reading Notes
Use these signals to refine the synopsis, topic links, people/company context, and method notes. If a source is a related external video rather than an exact official recording, keep it framed as supporting evidence.

## Transcript Status
No official session recording transcript was found by exact title match on the AI Engineer YouTube channel during this run.

## People
- [[anirban-chatterjee]]

## Notes
- Pending transcript synthesis when an official recording or confirmed matching video is available.

## Synthesis
### Synthesized Breakdown
# Guide, Verify, Solve: The Engineering Discipline Agentic Development Demands ## Conference Context - Date/time: 2026-07-01 · 11:40am-12:00pm - Track/room: Agentic Engineering · Track 8 - Speaker(s): Anirban Chatterjee - Session type/status: session · confirmed - Track: Agentic Engineering - Room: Track 8 - Session type: session - Status: confirmed ## Session Description Agentic development is not a productivity story: it's a reliability engineering problem at a scale most teams have never faced. Long-running agent tasks fail at alarming rates, pull requests have grown from 50 lines to 5,000, and cognitive surrender is real—the more capable AI output appears, the less humans interrogate it, right at the moment the stakes are highest. Independent, peer-reviewed research from Carnegie Mellon studying 807 open source projects found that AI agent adoption caused a persistent 30% increase in code analysis warnings and a 41% increase in complexity — with long-term development velocity declining as a result. Agents don't just write code faster, they accumulate debt faster, too.

### Speaker And Company Context
- [[anirban-chatterjee|Anirban Chatterjee]] — Director, Product and Solutions Marketing at [[sonar|Sonar]].

### Topics Covered
- [[agent-security]]
- [[agentic-search]]
- [[coding-agents]]

### Derived Links And Source Material

### Novel Concepts / Clever Methods
- No highlighted novel concept has been detected yet.

### Evidence Boundary
This synthesis is based on the official schedule and linked source pages. It should be revisited when exact session recordings or transcript-backed secondary sources are available.