London

June 28–29, 2027

New York

September 15–16, 2026

Berlin

November 9–10, 2026

How do you trust AI code you didn’t read?

What the LeadDev AI Code Review Report 2026 reveals about how developers review and trust AI code they didn’t read.


Date & time

17:00

Register for the panel discussion

Login or join LeadDev.com to view this content

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

Register with google

We have linked your account and just need a few more details to complete your registration:

Terms and conditions

 

 

Enter your email address to reset your password.

 

A link has been emailed to you - check your inbox.



Don't have an account? Click here to register

AI-coding agents produce changes faster than developers can read them, but engineers still own responsibility for the code they ship.

Drawing on the LeadDev AI Code Review Report 2026, this panel explores how software dev teams validate AI code they haven’t read, preserve understanding, and decide where human judgment belongs across the agentic SDLC.

We’ll look at how teams check changes against developer intent and codebase context, direct engineers’ attention to the most critical changes, and explain how those changes affect the wider system.

We’ll also discuss how security practices must adapt across the codebase, before and after deployment, as agents take on more development work.

Key takeaways:

  • Validate AI code changes against developer intent and codebase context
  • Prioritize human attention on the most critical code changes
  • Understand how AI-generated code impacts the rest of the codebase
  • Detect and address security risks across the codebase, before and after deployment

panelists:

Moderator: