Agentic coding in a large production codebase: wins, failure modes, and guardrails

Reddit r/AI_Agents News
agentic-coding production-codebase ai-coding guardrails verification engineering-practices human-judgment

Summary

Engineers across database, iOS, frontend, data engineering, and backend domains discuss how AI code generation shifts the hard part to verification and integration, requiring human judgment for subtle risks and architectural fit.

We recently interviewed engineers on our team across database management, iOS, frontend, data engineering, and backend domains about how AI is changing their day-to-day work. The most interesting theme was that the hard part came *after* the code was generated. Verifying behavior, catching subtle risks, and making sure changes properly fit the existing system/architecture requires human judgement. As AI makes implementation cheaper, how are you changing your review practices, onboarding, or expectations for engineers?
Original Article

Similar Articles

Agentic coding notes from Galapagos Island

Hacker News Top

Dan Luu reflects on his experiences using AI coding agents, noting that while AI can fabricate convincing but false repros, it still offers productivity gains in areas like debugging and testing. He discusses the balance of trust, automation, and quality in modern software development.

Agentic Code Review (15 minute read)

TLDR AI

An analysis of how AI coding agents have shifted the bottleneck from writing code to reviewing it, with data showing a 861% increase in code churn and a rise in defect rates, making code review the most leveraged skill in software engineering.

Engineering discipline

Reddit r/AI_Agents

A developer discusses the challenge of maintaining engineering discipline and architectural integrity when using AI coding agents that generate code faster than it can be comprehended, seeking best practices to avoid creating low-quality software.

Agentic Coding is a Trap

Lobsters Hottest

The article argues that agentic coding, where AI generates code and humans act as orchestrators, is a trap due to increased system complexity, skill atrophy, and vendor lock-in. It highlights the negative impact on developer learning and critical thinking, contrasting this new abstraction with historical programming shifts.