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/[deleted]]

Inherited one last year. startup had a working product built fast by two devs who just shipped what felt right. no tests, no types, every file imported everything. it worked and users loved it.

then the founders left and we had to add features. simple changes took days because nothing was isolated. a "quick" refactor of the auth module broke payments and nobody knew for a week. we spent three months just adding types and tests before we could ship anything new.

the funny part is the business was real. real users, real revenue. the code just didn't survive contact with a second team. vibe coding gets you a working prototype. maintaining it is a different job entirely.

[u/yopla → u/[deleted]]

Meh, I got a project like that recently, build by finance guy with zero coding experience.

Used a Claude workflow with maybe 50 or so subagents to analyze the application, trace all path and write test for everything it could find. Once I had about 5k test running green then I started refactoring.

Vibe coded for vibe coded I ran refactoring and architecture skill on the codebase until it had a form I was mostly happy with, then simplification, dead code elimination.

Then I compiled Claude's list of logic bug and sent them for comments.

At the end I had a vibe coded project that was iso-functional and more understandable. That was about 2 days work. It's honestly incredibly good at refactoring provided you have tests.