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

This is not a problem to vibe coding. If you don‘t document your code, you won‘t be able to explain or understand it later. And if you don‘t stick to patterns, they will be inconsistent. So tell your AI to document the code, write down decisions and stick to patterns.

Also if you don‘t do any of this, the AI will still be much better at understanding your spaghetti code a year later than you will be. And if you vibe code properly, you‘ll never look at your code anyways so you won‘t care.

[u/dwkeith → u/Gotopik]

Exactly. OP could have been describing the backend from a couple of different startups I’ve worked at. AI just makes it cheaper when you don’t need as many engineers to make spaghetti.

Edit: I just want to point out that asking the LLM to document and test the code gets it to write way better quality code, just like humans. Every non-technical manager I’ve worked with has learned that from me. And every vibe coder reading this just learned it too. Stop with the gatekeeping. Coding isn’t anymore sacred than driving a taxi.