Skip to content
Episode from the podcast DevOps Paradox
Why AI Coding Slows Down Code Review artwork

Episode

Why AI Coding Slows Down Code Review

Released Wednesday, June 17th 2026 55 min

Show notes

About this episode

#355: Picture your engineering team a year from now. A coding agent doing the coding. A testing agent on tests. A security agent on security. An infrastructure agent on infrastructure. All of them wired into GitHub and Jira, all of them working right alongside the humans. Not science fiction either - Atlassian and GitHub are already shipping these features. So out come the stats everyone loves to quote. AI code introduces 1.7 times more issues. Half of it ships with security holes. Code duplication is through the roof. AI-assisted PRs take four to five times longer to review. The response to most of it: so what? If you have a way to detect the issue and feed it back, that is just the SDLC doing its job. Couldn't care less if it is 1.7x or 50x more issues - what matters is what is left at the end, per feature shipped. Security holes? You have scanners. Detect, fix, ship. The only real problem is when you skip the detection or sit on the fix for months, and that has nothing to do with AI. Here is the one stat that actually sticks: PR reviews backing up. Speed up coding and leave everything downstream at human speed, and you have not sped up delivery - you have just moved the pile from Jira tickets to pull requests. The review pipeline was built for human speed, and now it is the bottleneck. The blunt fix: stop letting AI write 10,000-line PRs, work in smaller chunks, and accept that the job is about to get mentally harder. Delegate the tedious work and what is left is the demanding work - architecture, taste, is this even the feature we should ship. The silly stuff, does every function have a comment, is it camel case, goes to the machine. Spend your time there and you are wasting your talent. Offshoring never worked when the only goal was cheaper - chase the cheapest engineers, then chase even cheaper ones, and you end up dragging the work back in house. Same trap with AI. Offshore to Opus, then Sonnet, then Haiku, then Llama on a laptop. If cheaper is your primar...

More from DevOps Paradox

All episodes

KubeCon North America 2026 Review

36 min

#377: Every software company that ever thought about sponsoring KubeCon already sponsors KubeCon. So where does it grow from here? Ask what on the expo floor wasn't AI, and you get two answers: the coffee and the puppy petting area. Meanwhile, a lot of the session rooms were half full. We spent years pushing Kubernetes to be stable and ready for production. It is now. But stable and innovative are rarely the same thing, and if your company only pays for one conference a year, which one gets the ticket? In this episode, Darin and Viktor review KubeCon North America 2026 in Salt Lake City with our friend Whitney Lee.   Whitney's contact information:  LinkedIn: https://www.linkedin.com/in/whitneylee/ X: https://x.com/wiggitywhitney   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Secrets Management for AI Agents

41 min

#376: How many secrets can your coding agent reach right now? You gave it a token so it could get work done. It might have passed that token to every agent it spun up. Somewhere along the way, you stopped reading the permission prompts and started clicking allow. At the same time, hardcoding secrets in our code is still the most common answer for how secrets are managed. Developers get paid to close tickets, not to lower risk, and the agents just copy whatever they find in the repo. In this episode, we speak with Dwayne McDaniel, Principal Developer Advocate at GitGuardian, about managing secrets when agents are the ones using them, and why the better answer might be no secrets at all.   Dwayne's contact information: LinkedIn: https://www.linkedin.com/in/dwaynemcdaniel/   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

AI Writes the Code. Who Understands It?

49 min

#375: An agent can crank out 200 or 300 lines of code a minute. You can maybe review 40. So who's actually supposed to understand what just got merged? Maybe nobody ever did. Did you really read every line of every PR before AI showed up? Or did you just have the time? Now the junior has an agent, the senior is buried in review, and the job looks a lot more like management than coding. In this episode, Darin and Viktor talk about who's supposed to understand the code once AI writes it, and why that's now the senior engineer's job.   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Does AI Make Companies More Productive?

56 min

#374: Your company is paying for the AI licenses, and now there's a number attached. Two to three times the output, every day, or else. Can you hit it? If they're counting lines of code, sure. But you aren't the company. If everyone on the team gets faster on their own and the handoffs between them stay exactly the same, does anything ship sooner? Most AI today is single player. Your company probably isn't. In this episode, we speak with Tomasz Tunguz, founder of Theory Ventures, about why faster individuals don't add up to a faster company, and what that changes for startups and the people funding them.   Tomasz's contact information: LinkedIn: https://www.linkedin.com/in/tomasztunguz/ X: https://x.com/ttunguz   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Are Layoffs Really Because of AI?

45 min

#373: A company lays off 4,000 people the same day it posts record revenue, and the stock jumps. Is that really because of AI? Or just a really good press release? Layoffs used to mean a company was bleeding cash. Now they show up next to record quarters, and AI gets the credit. Doesn't matter much if you're the one who got rapidly reallocated. You still need a job. In this episode, Darin and Viktor talk about AI as the current layoff scapegoat and what to do when you end up on the wrong side of it.   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

This podcast, its content and its artwork are not owned by, affiliated with, or endorsed by Castquire.

Up next

  1. Nothing queued. Use + Queue on any episode to line it up.

0:00 0:00