London

June 28–29, 2027

New York

September 15–16, 2026

Berlin

November 9–10, 2026

AI coding made us faster. Why did incidents increase?

Faster code. Slower, harder incidents.
May 19, 2026

Estimated reading time: 7 minutes

Key takeaways:

  • AI amplifies whatever your delivery process already is. Strong practices get faster. Weak ones get paged at midnight.
  • The self-grading loop is your biggest hidden risk: when the model writes code and tests, it tests its own assumptions.
  • Observability is a release gate, not an afterthought.

Across engineering organizations, a pattern has become consistent. After rolling out an AI-coding assistant, velocity metrics improve quickly: pull requests (PRs) get bigger, cycle times shorten, and sprint records fall. Then, a few months in, the on-call rotation gets brutal. More tooling, faster shipping, and worse reliability.

Join LeadDev.com for free to access 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