Letting AI Approve Low-Risk PRs: What Worked in Production @infoq
Letting AI Approve Low-Risk PRs: What Worked in Production  @infoq
Uploaded October 2026 | Updated November 2026, 1 day ago
About 30% of code changes got no reviewer feedback. So the team let an LLM auto-approve the low-risk ones, and median time to merge dropped from about 18 to about 12 hours.

Sarah Deitke works on the DevEx AI team at Duolingo, where she helped grow AI tool adoption from about 80% to nearly 100% of engineers, then used that groundwork to build an AI risk-assessment bot that auto-approves low-risk pull requests.

Recorded at QCon London 2026. QCon conferences are practitioner-driven events where senior engineers share real production experience.

🔗 Transcript & slides available on InfoQ: bit.ly/46IRs8G

#AICodeReview #CodeReview #DeveloperExperience #AIAdoption #QCon
Letting AI Approve Low-Risk PRs: What Worked in ProductionThe MCP Megalith: Surviving the 1,000-Tool Explosion and Auth FragmentationAI Agents Won’t Save Your Engineering Culture - They’ll Ruin It FasterWhy Your App Crashes Under Load (Hint: Timeouts)  #infoqVibecoding your Own Multi-Agent WorkstationWhy Spotify Still Needs Humans to Code  #infoqArchitecting APIs in Regulated Industries: From 6 Months to 2 HoursFounders, Friction, and Focus: Building Engineering Teams at Early-Stage StartupsThe AI Revolution Fails Without Psychological Safety For Developers: A Conversation with Erin DoyleWill AI make junior & senior developers equal?30 Years in Tech: Why Your Career Ladder is Actually a Squiggle70,000 Lines of Code, 7 Languages: How to Scale via Rust Core
InfoQ |

Letting AI Approve Low-Risk PRs: What Worked in Production

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER