A r/gamedev thread (455 points) pushes back on the vibecoding narrative from the developer’s chair: Claude output works, but the architecture is “complete gloop,” and steering the agent costs more time than writing the code would. The replies turn the complaint into a practical checklist.
The complaint:
- The review tax — guiding and reviewing the AI takes longer than writing it yourself: “if im going to spend time anyway why not just do it myself with ai as a wingman.”
- Silent cruft — even successful generations insert unnecessary sections that “pile up” if you don’t catch them.
- Architecture loss — “I could of written all of it myself and have 1000 times better understanding of my architecture.”
The fixes the thread converges on:
- Mirror vibecoding (top reply) — invert the default: “it gives you the vibes and you do the code,” with AI handling fast review and suggestions.
- Document conventions first — several commenters say the real prerequisite is roughly 3,000 lines of docs encoding your structure and good practices before the agent can produce acceptable code.
- Guardrails over prompting — architectural decisions and infrastructure so you’re not prompt-engineering the same context and caveats into every request.
- Setup is the real cost — “your entire codebase needs to be setup with agentic coding in mind. Up to you if it’s worth it.”
- The floor — “you must know how to code… you should know what you’re doing.”
Both sides agree the bottleneck is architecture and context, not typing speed. The honest version of the pro argument — the agentic setup requires real documentation and infrastructure investment — is exactly what most tutorials skip, which is why “AI does the work” stories and “AI wrecked my codebase” stories can both be true.