
Sign up to save your podcasts
Or

![[Dev]olution](https://podcast-api-images.s3.amazonaws.com/corona/show/7206136/logo_300x300.jpeg)
What happens when the AI coder moves faster than the review process can handle?
Nnenna Ndukwe has spent 8+ years as a software engineer and now works at the intersection of AI, developer relations, and enterprise engineering strategy. As AI developer relations lead at Qodo, she spends her time helping teams separate useful AI adoption from expensive chaos.
In this episode of [Dev]olution, Nnenna joins Nicky Pike to talk about the part of AI coding most teams skip: review, verification, governance, and the outer loop where AI-generated code either gets controlled or breaks production.
They dig into why AI does not fix broken engineering systems, how rework rate exposes the truth behind AI productivity, and why better code review needs more than another stream of AI comments. What it needs, instead, are deterministic gates, developer trust, and a clear view of where AI belongs in the software delivery process.
If your team is shipping faster but fixing more, this episode will make you rethink what “AI productivity” actually means.
In this episode, you’ll learn:
Things to listen for:
(00:00) Meet Nnenna Ndukwe
(01:52) From writing code to advising leaders
(04:09) Why AI made the work more interesting
(07:02) Paying it forward in women in tech
(09:23) AI speed is breaking production
(10:30) Where the delivery jam really happens
(12:32) Why rework rate tells the truth
(15:42) Can AI review AI code
(17:21) AI amplifies your current process
(20:34) The risk of AI review slop
(23:19) Why acceptance rate matters
(26:27) Human-agent work needs better rules
(29:23) More tokens is not discipline
(36:44) Where leaders should start
(41:25) Predictions: More managing systems
(45:49) Defining a Coder: A problem-solver
(47:08) Final thoughts: Cut the noise of AI hype
Resources:
Nnenna Ndukwe’s LinkedIn: https://www.linkedin.com/in/nnenna-ndukwe/
Qodo website: https://www.qodo.ai/
By Coder
What happens when the AI coder moves faster than the review process can handle?
Nnenna Ndukwe has spent 8+ years as a software engineer and now works at the intersection of AI, developer relations, and enterprise engineering strategy. As AI developer relations lead at Qodo, she spends her time helping teams separate useful AI adoption from expensive chaos.
In this episode of [Dev]olution, Nnenna joins Nicky Pike to talk about the part of AI coding most teams skip: review, verification, governance, and the outer loop where AI-generated code either gets controlled or breaks production.
They dig into why AI does not fix broken engineering systems, how rework rate exposes the truth behind AI productivity, and why better code review needs more than another stream of AI comments. What it needs, instead, are deterministic gates, developer trust, and a clear view of where AI belongs in the software delivery process.
If your team is shipping faster but fixing more, this episode will make you rethink what “AI productivity” actually means.
In this episode, you’ll learn:
Things to listen for:
(00:00) Meet Nnenna Ndukwe
(01:52) From writing code to advising leaders
(04:09) Why AI made the work more interesting
(07:02) Paying it forward in women in tech
(09:23) AI speed is breaking production
(10:30) Where the delivery jam really happens
(12:32) Why rework rate tells the truth
(15:42) Can AI review AI code
(17:21) AI amplifies your current process
(20:34) The risk of AI review slop
(23:19) Why acceptance rate matters
(26:27) Human-agent work needs better rules
(29:23) More tokens is not discipline
(36:44) Where leaders should start
(41:25) Predictions: More managing systems
(45:49) Defining a Coder: A problem-solver
(47:08) Final thoughts: Cut the noise of AI hype
Resources:
Nnenna Ndukwe’s LinkedIn: https://www.linkedin.com/in/nnenna-ndukwe/
Qodo website: https://www.qodo.ai/