Date & time
17:00
Register for the panel discussion
Login or join LeadDev.com to view this content
AI has made writing code easy. Many engineering teams now say code review and validation is their biggest delivery bottleneck. Every extra AI-written change lands on the same reviewers, who are also expected to catch security flaws.
The technology for safe defaults mostly exists: MFA out of the box, encryption, and hardened APIs. The hard part is getting engineering teams to co-own security and sustain that ownership. Done well, it takes friction out of developers’ work, keeps risk from creeping up, and frees reviewers to focus on design and judgment.
This session brings together engineering leaders to discuss what makes delivery structurally safer as AI increases the volume of change. You’ll see how checks become part of how teams deliver, not a gate at the end, with compliance evidence produced as a by-product.
Key takeaways:
- Set a few non-negotiable defaults, with exceptions that are easy to request and always expire
- Put guardrails in the pipeline, so every change, human or AI-written, is validated the same way before a reviewer sees it
- Free reviewers to focus on design and judgment instead of catching what automation can check
- Build the shared goals between engineering and security that keep defaults in place