The author's description of vibe coding seems to have confused it with getting into a flow state in a vaguely AI-adjacent way. Vibe coding as originally coined by Karpathy [0] can't pay the bills because it would be wildly irresponsible for a professional to do—it's the kind of no-checks minimal-validation AI usage that gets lawyers into trouble for submitting legal documents with hallucinated court cases, just translated to coding instead of law.

What the author is proposing isn't really "vibe" anything, it's just dedicating a small amount of time to fixing tech debt in a way that happens to involve an LLM as an assistant. The LLM in this model is honestly mostly superfluous.

Don't get me wrong, this absolutely is how LLMs should be used in a professional setting, but I just question why we needed a name and a blog post for it. This is just responsible code maintenance as it's always been.

[0] https://x.com/karpathy/status/1886192184808149383?lang=en

Disagree gently here. Vibe refactoring is so much harder than vibe coding. I understand the temptation of having LLMs refactor code because that's ostensibly what they're great at – "transforming" the code. But LLM's are opinionated enough where they love to arbitrarily drop features or constraints for no particular reason, and they won’t tell you what they dropped along the way.

Proper refactoring with an llm requires full testing coverage and, by the time you do all that, is the refactoring really necessary? I prefer 100% stability. If you're refactoring the because it's poorly structured and unreadable, that’s okay.. LLMs can help understand it.

In my use of llms, i find it’s actually much easier to rebuild something from scratch rather than refactoring flawed code. It’s much less likely to inherit strange assumptions and code smells that way.

With all that said, the one prompt I do use when refactoring is to tell the llm to do a lossless refactor and then follow up with a "was this really lossless"? It's not foolproof. LLM's love to lie.

Refactoring is indeed one of the areas where LLMs already shine bright. And I love it.

I have been coding since I am 12 years old. I always loved writing code. But I also always loved reading code. I don't know, for me code is a kind of art. Never met anyone else who sees it like this. When a friend was hiring for his startup a while ago, I was happy to sit down for multiple hours and read all the code the applicants wrote and gave him advice on whom to hire.

So for me, the new times are paradise. I try to not touch code directly anymore. I write prompts that would enable a really good developer to implement features and then let various LLMs work on it. Afterward, I rate the results so I have an overall score for each LLM. I pick the best solution for my codebase and manually finetune it to perfection.

After each commit, I also ask the LLMs if they can find anything in the files that can be refactored to make the code shorter or more logical. The result is that the codebase becomes better and better. Because the LLMs often find stuff to improve. They usually come up with 10 ideas I dislike, but also one idea that I like. And so the codebase becomes better and better over time. Instead of worse and worse like in the past when you had to keep a balance of refactoring for the sake of beautiful code and building new features. Nowadays, refactoring becomes more and more free.

So, I know the battle has been lost for the definition of vibe coding (https://simonwillison.net/2025/Mar/19/vibe-coding/).

But we definitely need a word that makes a distinction between a LLM autonomously generating software, and having a human ultimately curating all the code (even if they're using a LLM to generate it.)

If not vibe coding, what should we call that?

Be _very_ careful about refactoring with Cursor -- it has a tendency to randomly delete important blocks of code and comments and re-order things in a way that make for difficult diffs to read. Make sure you do it in relatively small chunks and do PRs and have others review. The larger a refactor you do, the more difficult/impossible it becomes to actually review the code usefully.

I don’t really get what they’re doing. This would be a better article if they actually explained how they use repomix.

Did you use AI to write this blog post? Be honest.

Are we at the point yet where companies are looking for programmers specifically to fix their vibe coded codebases? A codebase restoration expert?

Or will they do what most companies do when they sink millions of dollars into a codebase that doesn't work: dump the codebase, dump the team, hire a new one, and build from scratch?

What does everybody think?

edit: oxford comma is life.

I tend to use tools like ChatGPT to refine my code.

i.e. "I have this function. Can you suggest ways to make it more efficient?" etc.

Sometimes, it gives good feedback, sometimes, not. I almost always need to modify whatever it gives me.

Are any of the freelance software dev marketplaces seeing an uptick in opportunity to refactor vibe code?

Probably an opportunity to category kill that niche.

"Got a vibe coded prototype you want to make more robust?"

We've reached the stage where the word vibe in a coding submission is a really good indicator that you should just flag it and move on. It is a meaningless, incendiary, click-bait term that is meant to trigger people and induce engagement.

"There’s a lot of hype about vibe coding"

There is incredibly little hype around vibe coding. 99% of the comments about vibe coding are people propping it up as a strawman to knock down. Otherwise it's like it fills the void left by web 3.0's decline to irrelevance where a bunch of useless masturbatory noise is had by people trying to get in front of something that they think will be a thing. Maybe they can put it on the blockchain.

All of us normal people incorporate LLMs into our work process. No vibes at all. Just another tool in our belt.

EDIT: Just discovered that my comment is apparently dead by default, which is...interesting.

So this is a plug for repomix?

Some questions,

Does repomix do anything Github copilot should be doing? It seems like this should be something copilot does automagically.

Does it work on any language? I notice the repomix github suggests a different tool if you're using python.

It seems straightforward to create an output.xml on the repomix site, but is there an opinionated try-it-free AI to use that output with?

I'm tired of trying things only to get ai slop. If this cures the slop, I would be interested.

edit: it seems the HN discussion is dominated by the definition of "vibe coding" and not at all interested in what the article presented as a solution... nice.

can we just ban llm-generated blogspam submissions already

Hiring a bunch of recent college grads to build your startup is fun. They're great drinking buddies and they make you feel young again. They'll inefficiently work around the clock, sleep at the office, and treat it like their mom's house, and make you think you're a big, important boss.

Coming in as a gray hair to fix their disaster definitely pays the bills.

I wont feed my production code to a LLM thanks for trying though. There is not a single trustworthy "AI" company out there. My companys codebase is a complete dumpsterfire and I will extinguish with a complete rewrite later this year. There is nothing, absolutely nothing worth paying for when it gets to LLMs.

> I also ask the LLMs if they can find anything in the files that can be refactored to make the code shorter or more logical

Citation needed? The worst kind of code tends to be clever code. This seems like a lot of code churn for no real benefit other than some loose definition of "better". How do you prevent bugs with these constant refactors?

Man, I must really suck at this stuff. This is not at all my experience. Asking LLMs to refactor almost always results in hasty abstractions that I want to keep out of my codebases at all cost. Am I not letting go enough?

As the author of this article/video - it's really strange for me that almost everyone here in these threads has focused on the LLM part of refactoring, where it's only mentioned as one of many tools for target-less flow state of the code tweaking sessions. :-)

Simply coding. It's going to be AI-assisted by default. It already is for students getting into programming, and it'll take some years for old people to pick up these tools too, but I imagine we'll get there pretty soon.

Where do you draw the line though? Is it only vibe-coding if you don't touch a single line of code? If I ask Cursor agent to implement a basic refactor vs doing it by hand, does my level of "vibe" increase?

Why do we need a term anyway? Neologisms are nice for writing articles but I feel like we get lost in the weeds unnecessarily trying to categorize things. Its like trying to come up with genre names for electronic music. The more terms we create, the less useful they become.

I always thought of it as a temporary term anyway while we reconcile this technology with the status quo. In a few years I'll bet it will go back to be just "programming" or "development".

Judging by the younger group coming out of college that I interact with, it's just coding. This is just how it's done now.

It's going to be a spectrum so will be hard to divide up.

I know a crash-course-day's worth of programming language(python and C), but very strong understanding of the principles of programming. So LLMs are a godsend because I can basically write code, function by function if need be, in English.

"Create this variable, do these mathematical transformations on it with retrieved value from API, display the output of it here, also compare it to the output of everything in the test set, store differences greater than 30% to their own set, store all values in an SQLite database, create a simple GUI with a field showing each output, make a button that outputs the results to a .pdf, give it a title block with labeled results listed, etc. etc."

Does coding become vibecoding when you do it in English? hah

What do you call coding with Intellisense? What di you call coding while referencing documentation?

I find this happens for pretty much every name that doesn't actually match what it is suppose to describe.

In this case, most people have to be told what "vibe coding" is. I think hardly anyone guesses what it is by just hearing the name.

So I'm not at all surprised that people are using it to mean other things already.

pAIr coding? pAIr programming?

One is coding, the other is ordering.

Otherwise all my customers/bosses did vibe coding way before LLMs.

What do we call emails that have been spell checked?

Why do we need a term for any of it, other than "coding". Before AI, I did not need different terms for coding when some devs would cowboy-code buggy slop straight to production vs. a full team doing test-driven development with dedicated QA staff on top of it, or anywhere in the middle. Vastly different qualities of work, but the same term - "coding".

So why do we need a term? What difference in action will hearing a different term drive?

On that front, I like the fact that the term "vibe coding" exists because anyone who uses that term unironically has just told me that they care more about the process than the result. Now that is information that changes my actions because it changes how seriously I take them.

Lazy coding

AG code?