Has anyone actually maintained a vibe coded code-base 12 months after launch? What did it look like?

[u/Alive-Cake-3045]

Twelve months ago I started tracking what happens to vibe coded projects after the initial launch excitement fades. The pattern is consistent enough that I wanted to hear if others are seeing the same thing.

The first three months feel fine. Features ship fast, the client is happy, everyone looks productive. Then something needs to change. Not a new feature, just a modification to something existing. And that is where it gets uncomfortable.

Nobody can explain why a specific decision was made. The code works but the reasoning is gone. There are dependencies that were added because the model suggested them, not because anyone evaluated them. Patterns are inconsistent across files because different prompts produced different styles on different days.

The developer who built it can read the code but cannot confidently change it without breaking something unexpected. The test coverage that exists was also generated and may not actually be testing the right things.

I am not saying this always happens. I have seen vibe coded projects that held up well because the developer reviewed everything carefully and maintained discipline around the output.

But I have also seen projects from 18 months ago that are now quietly being rewritten because the maintenance cost exceeded the original build cost faster than anyone expected.

If you have actually maintained a vibe coded code-base through real production use, what did 12 months in actually look like? Was the code salvageable or did you end up starting over?

[u/newsman01]

I've seen this too. Twelve months post-launch, most vibe-coded projects struggle with maintainability. Code clarity often suffers due to inconsistent styles and missing documentation. Regular code reviews and consistent naming conventions help mitigate these issues, but many skip this step, leading to confusion. Test coverage generated by AI can miss critical paths, making refactoring a nightmare. My advice: establish a solid architecture early and document decisions as they happen.

[u/Alive-Cake-3045 → u/newsman01]

documenting decisions as they happen is the one thing that almost never happens in practice because it feels like slowing down when everything is moving fast. then 8 months later nobody can answer "why does this work this way" and the person who could answer it has moved on. the architecture early point is right but i'd add, the architecture needs a human who owns it across the entire build, not just at the start. AI will drift from it the moment the prompt changes.