camsoft2000’s thread on X puts words to a problem that’s been lurking behind a lot of AI-assisted coding success stories: shipping features is getting easier, but keeping a growing codebase coherent can get harder—fast.
The core complaint isn’t that the agent can’t build. It’s that, over months of iteration, the accumulated output starts to look like copy/paste drift: repeated patterns that begin life identical, then diverge into “loads of similar but slightly different blocks of logic.” The result, as described, is a project that still “works,” but is increasingly fragmented, inconsistent, and difficult to reason about—for both the human and the agent.
When “it works” stops being the bar
A recurring theme in the thread is the gap between prototyping and productizing. “Vibe coding something into existence” still feels “magical,” but “turning it into a mature product with months of iterations is painful.” The author frames the current reality as a choice between:
- a complete rewrite (leaning into the idea that code might become more disposable), or
- continuing to fight entropy as each feature takes longer than the last
Notably, the thread calls out that plenty of “anti slop” techniques are already in play—plans, docs, validation—yet the outcome feels similar. That sets up the real point: tooling can help, but architectural consistency is a different kind of work than just passing checks.
The replies: discipline, guardrails, and “agents don’t see the codebase”
The responses range from pragmatic to philosophical. One early reply argues for “as much deterministic validation as possible before a commit happens,” listing pre-commit hooks, custom linter rules, knip, and jscpd, plus an AGENTS.md file to steer agent behavior.
Others echo the experience more directly, including the hope that future agents will be able to clean up what today’s agents create—followed by the sharper observation that this hope is part of what keeps people hooked.
There are also pointed one-liners that capture the failure mode: “Agents don’t see the codebase. They see the prompt,” and the reminder that “the code works perfectly” can be “doing a lot of heavy lifting when you can’t read it six months later.”
The full thread is worth reading for the candid details and the spread of coping strategies. Source: https://x.com/camsoft2000/status/2035828197670174835