[sixtyj]

I see your point.

Last time I “vibe coded” something (internal) and I liked it because I couldn’t find external solution.

I admire coders who can finish their code into deliverable and usable piece.

Issue here is software abundance and ppl will start to hesitate due to absurd pile that they should evaluate.

It reminds me the statistics of ice cream global sales. People want certainty so they choose chocolate or vanilla :)

Therefore many good software projects will have a problem to find users.

[swasheck]

i think we need to encode (or refine) what we mean by “vibe code.” my original impression was that it was used to describe the process whereby someone with an idea but lacking development/engineering skills leveraged llm via an agent to create the mechanics to bring their idea to fruition. anymore it seems like if it has the hint of AI then it’s “vibe coded.”

ironically, i didn’t read the article because i come to comments now to see if its been identified as AI slop, so i don’t know which area this falls into

[dghlsakjg]

Definitely. The original vibe coding tweet is pretty explicit about “forgetting the code exists”, and “throwaway weekend projects” (https://x.com/karpathy/status/1886192184808149383)

Now however, many people just use it to mean any ai-assisted coding.

One person says “vibe coding” to mean a throwaway script to scrape some page. Others use it to mean a code reviewed app built by a team using Claude.

It is so broad as to be meaningless at this point

[theshrike79]

Some people (me included) are trying to separate Vibe Coding (no idea about code, just give me the result) from Vibe Engineering (I know how to do this, but can't be arsed to write. I also know what the result should look like)

[sixtyj]

Cool. Thus I am an ai/llm-assisted coder amateur. I don’t code for living, I know principles (or I think so) but don’t remember syntax (too old to learn new tricks :)