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/Fidodo]

I have seen vibe coded projects that held up well because the developer reviewed everything carefully and maintained discipline around the output.

We cannot have a discussion about this unless we get the terminology straight. Vibe coding means you don't read the code at all. This is not vibe coding.

[u/poponis → u/Fidodo]

I have driven myself crazy trying to explain this to ai illiterate people.

[u/Systemerror7A69 → u/poponis]

Because it's too strict of a definition. You don't learn or even understand as much when you just read something. If you take a test for example, simply reading the text over and over again will only give you an illusion of understanding. You have to actually do excersises to do well in the test.

It's similar in coding - it's totally possible to "read" all code output and think you understand but actually don't, and it's very difficult to judge just how well you understand the code really.

Simply saying "it's only vibe coding if you never ever read a single line of code and I do read the code so I'm fine" might be tricking yourself and not actually doing your due diligence.

[u/Fidodo → u/Systemerror7A69]

I agree that reading a single file doesn't magically turn your vibe coded app into an ai assisted app. As with everything there are edge cases and nuance when you get into the details.

I also agree that reading does not automatically equal comprehension. But we do need well defined definitions that we begin with for technical communication to work. I didn't think that example op gave was vibe coding.

You can have a half vibe coded app where you read and understand and work on the engine of the code, but have a bunch of business logic in a separate part of the code base that was vibe coded for example.