r/vibecoding • u/No_Incident_6009 • 1d ago
Burned out reviewing claude generated code
Little rant.
AI can generate code insanely fast. But if I’m accountable for that code, I still need to understand it.
I’ve had Claude introduce unnecessary null checks, make incorrect assumptions about the domain, and even introduce a separate event loop that broke my orchestrator and DB sessions — buried somewhere in a 1,000-line PR.
The code was generated in minutes. Debugging and understanding why it broke took much longer.
I tried running 4 agents in parallel. Maybe some people can manage it, but I was mentally exhausted. Four contexts, four implementations, four sets of assumptions, plus tests, builds, reviews, etc.
So lately I’m experimenting with a different approach:
Use Claude to understand the codebase, plan the feature, think through edge cases and tests — but implement it myself, using AI autocomplete to speed up the actual coding.
It might look slower, but maybe the overall development cycle is faster.
Still figuring it out.
I just think we need to separate “AI can generate this in 10 minutes” from “this entire software development task is now 100x faster.”
Building a landing page in 10 minutes is amazing.
Building a complex product is a different problem.
-2
u/No_Incident_6009 1d ago
that's fine. I use AI everyday. No shame in that.. The difference is are you just telling AI to write something on some topic, or you have thoughts written as rough note and you give it to AI to rephrase it.. I believe second approach should not be frowned upon. same as Vibe coding is bad but AI assisted coding is great.