Vibe coding feels faster right up until your project becomes big enough to remember its own history

Reddit r/AI_Agents News

Summary

The author reflects on how AI-assisted coding boosts initial productivity but warns that larger projects require deep codebase understanding, necessitating better documentation and code literacy practices.

I was very productive in the first 5 weeks of a client project. I made prompts, added features and the agent shipped it in a week and demos were completed every Friday. I started wondering why I spent years typing code by hand like a medieval scribe. Then on 6th week the client asked a question about a system with my name on every commit: why do the totals round the way they do? and I had no idea and then I spent the evening debugging my own codebase (Basically Git-blaming myself). I've been building software for other people for eight years and whatever the contract says, the actual job has always been answering for the code later. The code gets written maybe ten times faster now and I read at the same speed I did last year. So the project didn't get hard because it got big rather the understanding of it turned into the main job. On client work it goes past my own understanding too, since whoever they hire after me will have questions and those questions will have my name attached. I had been trading codebase literacy for speed without writing the trade down anywhere. What I do differently now is that I read the agent's writing while they were writing and I log the reasoning behind decisions. I also write a line item for the time I read the quotes.
Original Article

Similar Articles

Am I the only one starting to get 'Vibe Coding' fatigue ?

Reddit r/AI_Agents

A developer shares their fatigue with 'vibe coding,' noting that while AI agents speed up initial creation, they introduce significant architectural debugging challenges and technical debt in complex repositories.

How Do We Stop Vibe Coding?

Hacker News Top

The article discusses the rise of 'vibe coding' using AI agents, its risks to code quality and developer understanding, and calls for rethinking software engineering practices to move beyond merely generating code from intent.

Vibe coding and agentic engineering are getting closer than I'd like

Simon Willison's Blog

Simon Willison reflects on how vibe coding and agentic engineering are converging in his own workflow, raising concerns about code review responsibilities as AI coding agents like Claude Code become increasingly reliable. He explores the ethical tension between trusting AI-generated code in production and maintaining software engineering standards.

VibeCoding with AI Agent is not enough, you need more insight

Reddit r/AI_Agents

The article argues that AI-assisted coding (VibeCoding) lacks production readiness, emphasizing the need for deeper insight. It references a conversation with an FDE engineer and notes that CloudCode cannot be used directly on customer sides.

The biggest trap I've hit doing "vibe coding" as someone who's never written code

Reddit r/AI_Agents

A non-engineer shares that the biggest pitfall in AI-assisted 'vibe coding' isn't prompting but verifying whether an AI fix truly solves the root cause or just patches a specific case, leading to fragile code. Offers practical tips like asking if a fix is general or special-cased, and maintaining a living design doc.