3 ms·

A particularly insightful nugget in this article was your definition of vibe-coding from an experienced insider: "Ignoring the code entirely and only prompting"

A particularly insightful nugget in this article was your definition of vibe-coding from an experienced insider: "Ignoring the code entirely and only prompting". I've struggled with the definitions and wondered where the line is drawn. In private, I'm more strict with how I define vibe coding: "Prompting for information about code". However, it's strict so that I don't become dependent on AI while we're still discovering the harms. It's unfortunate that head count is considered a cost to some. I always found that the people in an organization should be considered as important as profit. Where increasing headcount is as positive an indicator as increasing profits. I'm not sure how our economy came to this point, perhaps it's a symptom of our short-term financial planning.

GeneralMayhem 11mo ago
"Ignoring the code entirely and only prompting" is the only definition of vibe-coding I'm aware of. It's from a Karpathy tweet (https://x.com/karpathy/status/1886192184808149383 https://x.com/karpathy/status/1886192184808149383): > 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... I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension. It specifically doesn't mean "using an LLM as a code assistant". It definitely doesn't mean asking the LLM questions about code which you'll then use to write your own code. Those are LLM-assisted activities, and it's totally fine if you're using the LLM that way. But it's not what the term "vibe coding" means. "Vibe coding" is giving up on any pretense that you're in control, and letting the LLM take the wheel. It's fun for getting quick projects done, but it's also now becoming a distressingly common practice for people who literally do not know how to program in order to get a "product" to market.
fatihpense 11mo ago
I agree that the vibe-coding definition is helpful. Ideally, headcount can be seen this way: our company is giving many people the chance to do honest work and live dignified, meaningful lives. I think that should be a company's main social responsibility not superficial marketable stuff.

GeneralMayhem 11mo ago

"Ignoring the code entirely and only prompting" is the only definition of vibe-coding I'm aware of. It's from a Karpathy tweet (https://x.com/karpathy/status/1886192184808149383 https://x.com/karpathy/status/1886192184808149383): > 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... I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension. It specifically doesn't mean "using an LLM as a code assistant". It definitely doesn't mean asking the LLM questions about code which you'll then use to write your own code. Those are LLM-assisted activities, and it's totally fine if you're using the LLM that way. But it's not what the term "vibe coding" means. "Vibe coding" is giving up on any pretense that you're in control, and letting the LLM take the wheel. It's fun for getting quick projects done, but it's also now becoming a distressingly common practice for people who literally do not know how to program in order to get a "product" to market.

fatihpense 11mo ago

I agree that the vibe-coding definition is helpful. Ideally, headcount can be seen this way: our company is giving many people the chance to do honest work and live dignified, meaningful lives. I think that should be a company's main social responsibility not superficial marketable stuff.