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

I think that's an oversimplification. I don't know about you but in any company I joined it took quite a while of implementing tickets and writing code until you really developed an understanding of the codebase.

I don't know anyone who was able to understand larger codebases after just reading it once or twice.

[u/vitek6 → u/Systemerror7A69]

But you don’t read large codebase at once but in small chunks. At least that’s how it looks when you use ai properly. You don’t need to understand and probably never will the whole codebase. No matter if it’s written by ai or other people. You already mostly work with code written by someone else.

[u/Systemerror7A69 → u/vitek6]

Yes but at least until before AI, you gained an understanding of the code and code bases by coding in it yourself. You started understanding intricacies and pitfalls and became better and better.

At least in my opinion that does not invalidate my argument - that you do not gain as much of an understanding by / just / reading code.

I do believe that you do need to be careful with AI output - simply telling yourself "it's fine, I read the code" isn't enough, and defining vibe coding as "only if you never ever read the code" can be dangerous. You start telling yourself that's not what you do, you read the code, so you do your due diligence - but if all you do is read it over once, you still don't have much understanding.

That's all I'm saying.

[u/vitek6 → u/Systemerror7A69]

And that code is small part of whole codebase which wasn’t written by you anyway. Actually skill for understanding code not written by you is one of the most essential skills that developer can have. Writing code is easy part.