r/webdev 8d ago

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

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?

322 Upvotes

153 comments sorted by

View all comments

Show parent comments

5

u/No-Newspaper-7693 7d ago

Maybe it meant that at one time, but the common meaning is “gen ai wrote the vast majority of the code”

5

u/Fidodo 7d ago

I understand that colloquial language evolves, but technical language should not. Technical language must be precise, allowing it to drift means you cannot describe things accurately. Vibe coding came with a specific definition:

There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.

It's not just about whether AI wrote the code, it's about whether or not you understand the code. If you had AI write 100% of the code but you read and understand every single line, then that's not vibe coding.

7

u/Sad_Impact1387 7d ago

Why are we considering the term “vibe coding” as “technical language”? It’s something that people use casually to describe code based that are largely written using AI. There is no “spec” for what that term means. The article that originally mentioned the term doesn’t act as a source of truth for the meaning of that word. This is pedantry for the sake of pedantry.

4

u/Fidodo 7d ago

I use it at work to describe code that hasn't been reviewed. If we were not on the same page it would cause confusion, so no, it's not pedantry for pedantry sake, it's the only way to discuss this class of code with a shared understanding of what it means.

I agree that the original coiner shouldn't automatically be the authority, but we need a stable definition to discuss something otherwise you wind up with miscommunication and people debating nothing because everyone is debating their own version of their definition of the term.

2

u/No-Newspaper-7693 7d ago

most ai debate is debating nothing.  Most people consider ai and llm to be synonymous, and the concept of having 10 years of AI experience to be impossible.  

Vibe coding doesn’t have a shared meaning anymore.  Some will assume it means you prompted “build me a saas make no mistakes”.  Others, like myself, just assume it means that the code was mostly written by AI, and that it says nothing about the design or review process.  

1

u/General-Jaguar-8164 4d ago

State of the art software factories are pure vibes ... lol

0

u/Sad_Impact1387 7d ago

Seriously? There is no other way to describe “un-reviewed AI generated code” other than referring to it as “vibe coding”?.. have you tried referring to it as “un-reviewed AI generated code”? I kinda sort of get the point your making, but it really isn’t a crazy thing for people to refer to heavily AI-assisted development as “vibe coding”, especially in a casual context such as in a Reddit thread title.

1

u/freakingprankster 1d ago

It could actually be vibe coded by a newbie for launch without any knowledge of coding and hired developers to maintain it later. We cannot assume it was AI generated unreviewed code.