> Buying a domain is not something you have to do daily to require any kind of automation
I wrote a python client for dnsimple nearly 16 years ago to exactly that. If you can’t think of a reason it’s useful, you may wish to get your agent to buy a domain for some project you have asked to create.
> I suspect it's less of an undertaking than you may think... having an existing codebase you can reference prevents a lot of the problems you have with vibecoding.
Yeah, it's a distinction worth making, and the language for making it kind of sucks. Vibe coding means "AI does the whole thing", or "I use tab autocomplete" depending on who you ask. It's not a very useful term anymore, we need better ones.
My benchmark is basically, "are you letting the AI drive."
In this case, an AI appears to have written the migration guide...
It was and is a perfectly good term, but people started using it without regard for its definition. I don't know why people wouldn't misuse a "better" term the same way.
In this case I think the current zeitgeist (at least among zoomers and younger millennials) really loves the word "vibe". Once they hear of the term "vibe coding", they just want to be able to say it, even if what they're doing isn't really vibe coding.
And then that leaks outside their social and age groups, because other people hear the incorrect usage, get confused, and incorporate that confusion into their own use of the term.
You are right but recently, vibe coding has become a demeaning term for AI assisted code by anti-AI people. It’s interesting seeing how words evolve very quickly on the internet as they spread to different demographics.
Just going off vibes and not even looking at the code was the original definition. But "different people say the same thing but mean different things" is kind of the problem I was getting at.
The definition is at https://x.com/karpathy/status/1886192184808149383 and no that does not match what is in the branch. Systemically migrating a code base using an LLM does not match the defintion of vibe coding.
> I’m seeing people apply the term “vibe coding” to all forms of code written with the assistance of AI. I think that both dilutes the term and gives a false impression of what’s possible with responsible AI-assisted programming.
Then "vibe coding" is a useless term, if it just means "LLM-assisted coding". We might as well just say "LLM-assisted coding" or "AI coding" or whatever.
As much as I find the word "vibe" generally annoying (in all contexts), I actually really like "vibe coding" as "LLM did everything and I didn't even look at it". It's a succinct, useful way to describe that mode of doing things. Diluting it down to "LLM-assisted coding" makes it useless.
Nah, I'm not big on these "it either matches the way ___ used it or it's useless" binaries. The term is the term, it's recent, and people are using various forms of the others you mentioned. People use it loosely, people use it specifically, this is the way for many colloquial terms, and definitions form around them and expand over time or change.
It sort of surprises me how uptight people are getting about a term that was mentioned on X last year and has since been tossed around to loosely imply that a machine did between zero and all of the work. Just because it doesn't match exactly does not mean it's useless, it maps to a concept, if the details are important and ambiguous, then elaborate.
All language is "coined terms". The point is that if you dilute the definition of a term, you make the term useless. Evolution of a term isn't done automatically. Correcting terms such as these pushed the evolution in a more useful way. Also, evolution of language is not a magic spell that automatically forgives people on making language mistakes.
I think the definition of vibe coding is a bit fluid, in this case I just meant it to be “code fully generated by AI, possibly not fully reviewed by human eyes”. I agree that this definitely not “coding based purely off vibes”, and the approach looks legit.
The question isn't whether or not you'd get the same line count with a non-LLM tool. The question of whether or not it's vibe-coded depends on whether or not the committer actually reviewed and understood the new code. And with a 75k line difference, that seems unlikely.
It depends on what you mean by "vibe coding". Is AI coding based on an existing implementation vibe coding? What about only from a natural-language spec? How does manual reviewing affect whether or not it's vibe coding?
> How does manual reviewing affect whether or not it's vibe coding?
I think the most commonly-accepted definition of "vibe coding" is when you "forget that the (generated) code even exists"[0]. So vibe-ness entirely hinges upon whether you're manually reviewing. If you make/prompt changes based on what you observe in the generated code (rather than only based on runtime behavior), then you're not "vibe coding".
I think the other things you mentioned are orthogonal to vibe-ness.
In practice all use of AI rapidly becomes vibe coding. Even if someone says they're going to carefully manually review everything that's generated, within a couple of days they get bored and just click approve.
This is just a matter of priorities - I use LLMs to write code every day and I have never put a single line of code up for review that I didn’t read and understand.
I use to do this and then do test manually to validate everything works as expected in my small open source project. But then over the time I saw that some bugs crept in which I was unable track since I was doing manual testing. So I wrote some e2e tests with playwright and I think that gives a bit relief (at least).
The really interesting thing in the UK is that both team X and team Y absolutely love flags - the right loves putting up English flags in town, the left loves protesting with Palestine and occasional Hamas or Hezbollah flags.
To the best of my knowledge Linus Torvalds isn't posting walls of text to Github breathlessly announcing he's 810x-ed [1] his "logical lines of code/day" compared to what he was doing in 2013.
And, lest you think generating "600,000 lines of production code in 60 days" [2] is potentially problematic, has also fully solved the primary failure modes of AI coding identified by Andrej Karpathy, once and for all: "Karpathy's four failure modes? Already covered." [1]
As someone who has experienced mania, including with a programming bent specifically, it's hard not to raise an eyebrow at the idiosyncratic human-y bits of his thinking floating up from the sea of em-dashes and it's not X it's Y in his manifestos.
Plus volunteering this [3] in an interview:
“I sleep, like, four hours a night right now,” he told his interviewer, fellow VC Bill Gurley, during an onstage interview Saturday. “I have cyber psychosis, but I think a third of the CEOs that I know have it as well,” he joked about his current AI obsession. (Tan’s assistant confirmed to us that he was joking. ...)
It’s like I was able to re-create my startup that took $10 million in VC capital and 10 people, and I worked on that for two years, and I took anti-narcoleptics — I remember, you know, sort of being on modafinil...
(Not who you responded to.) You clearly don't know anyone who lives with a condition that would cause manic episodes.
They're terrible. Imagine being super focused and productive and excited by how much you're accomplishing as you're banging out innovative code and solving complicated problems with brilliant elegant solutions. Next thing you know you've been awake for two days and your mind no longer works but you're still super motivated and trying to make sense of what you're working on but it no longer tracks and you literally can't keep a line of code in your head long enough to combine it with the one that comes after it. And then you give up and try to watch streaming content for the next two days while your body begins to hurt terribly and you're dehydrated because you kept forgetting to drink water and you can't follow any plot-lines and your mind is mush and then when you finally fall asleep you wake up feeling like you got hit by a truck because you're so undernourished because you had no appetite for much of the episode and your body is literally failing / on the way to starvation.
For bonus points, you might even experience disordered thinking with hallucinations and paranoia and think someone has hacked into your computer and is trying to frame you for crimes and then destroy all your devices and drives, which I did once late at night before things got much worse and I came to in an ER and had to be restrained. It's super cool.
Calling out signs that someone might be experiencing this type of disorder is not being critical of their passion. It's putting notice out that they might not be operating in the same reality that you and I currently occupy.
Just commenting to say, from a place of empathy, that you're right and that it's hard for people to understand what mania looks like in someone if you haven't experienced it first-or-second-hand. You see it a few times and it becomes obvious. In the moment it can be disorienting and cause you to question your own reality because theirs seems so influential and motivated. I hope you're doing well these days.
> My mother has bipolar disorder, but please, tell me more about my life experiences.
I told you about mine, not yours. And her bipolar experience also isn't yours. You didn't go through that, but I did and she did. You experienced it by proxy.
I only dream of a Grey Tribe equivalent of Grok that's actually not embarrassing to use. If the goal of technology is to elevate the human condition, then woke excesses should be treated, not amplified, by the use of tech.
I wrote a python client for dnsimple nearly 16 years ago to exactly that. If you can’t think of a reason it’s useful, you may wish to get your agent to buy a domain for some project you have asked to create.
reply