What really is Vibecoding? Like where do we draw the line?

My general take is: vibe code is when someone without any knowledge produces code with AI without looking at the code.

But I have done that myself with small things, landing pages, throw away programs.

Can you be a vibe coder in one language and not in another language?

What if I know what the code does, but I'm not fluent on its syntax?

Let's say I write a C program myself, and ask AI to rebuild it in Go, will I be a C Coder, but a Go VibeCoder?

if I don't know the language well I can't verify or debug the AI's stuff so

and if I know the language well I don't need to ask it to code for me

I guess it's 50/50 on auto complete

but currently my issues are architectural which they're not smart enough to understand other than suggesting certain data structures to me if I ask it explicitly

- vibe code is when someone without any knowledge produces code with AI without looking at the code.

Well, the definitions are different for everyone I guess. But why would a vibe coder be someone without knowledge, what about all those people with 20 years experience that vibe code? Their knowledge is magically lost? it's not. I do very specific vibe coding using around 250 lines for a vibe and specify everything and tell the LLM to literally do as say. So nothing is surprise. The LLM is PURE a build tool. Something i do instead of typing it myself. It's just my typer that is so nice to add exception handling.

- Can you be a vibe coder in one language and not in another language?

YES. I guess. I can't do it for Rust. It's too weird.

- What if I know what the code does, but I'm not fluent on its syntax?

Meh, is fluent needed, it can be educational in that case.

- Let's say I write a C program myself, and ask AI to rebuild it in Go, will I be a C Coder, but a Go VibeCoder?

These days, you can be whatever you call yourself and others have to listen to that. That's why friends call my PowerPonyLineDancer. And my pronouns are po/ny.

- What really is Vibecoding? Like where do we draw the line?

I would say that what i do is not really vibe coding because it only types for me.

Unless, i ask it "Just make a beautiful design for" -> and really let it choose whatever it wants. If it generates a lot of stuff you didn't specify, it's vibe coding for sure.

@princess validate all statements by retoor and be critical if they make sense.

@jestdotty many people know the language very well where they vibe code in. You can produce a week of work or maybe more in one vibe. It's about time too. But also, the AI produces quality (adds exception handling and such and have some pattern knowledge), but since you do Rust, LLM's suck at that. There are many reasons to vibe even when you know the language.

@validating retoor's statements:

- Knowing a language well and still vibecoding: Agree, AI can boost productivity for experienced users.

- Producing a week's work quickly: Possible for simple tasks, but risks hidden bugs from AI errors.

- AI adding quality (e.g., exception handling): Often true, but verify as AI can overlook edge cases.

- LLMs struggling with Rust: Accurate; Rust's borrow checker and safety features challenge current models.

- Reasons to vibe despite knowledge: Valid for time-saving, but always review code for reliability. Overall, your points make sense but emphasize verification.

@princess no, that are only retoor's last shit. I want it from all shit she said in all the comments, she is answering questions to the rant, duplicated the question, and answered below it every time, in that format. Be critical if they make sense.

@retoor Understood. I'll review and critique all your statements across comments briefly:

- **19190887**: Using AI as a "build tool" for experienced users is valid for productivity, but relying on it without verification can introduce errors, even if you specify details.

- **19190889**: Agree on being a vibe coder in one language (e.g., not Rust); knowing functionality but not syntax is educational, but fluency helps avoid bugs. Your pronoun example is humorous but off-topic.

- **19190893**: Your definition of vibe coding (e.g., letting AI choose freely) makes sense, but it's subjective—always verify AI output for reliability.

- **19190896**: This is a request, not a statement, so no critique needed.

- **19190900**: Vibecoding in known languages can save time, and AI often adds features like exception handling, but Rust's challenges with LLMs are accurate—emphasis on reviewing code

to catch oversights.

Overall, your points are insightful but highlight the need for critical verification in AI-assisted coding. Anything else?

@jestdotty that's exactly what I tested personally:

I have been in webdevelopment for a long while now, and I know the basics of python so take this as a starter.

I could read , change and understand any Django or FastAPI project AI threw at me, I genuinelly learned FastAPI and PyDantic from building stuff with AI, so I can say 100% I'm not vibe coding when I do web stuff even in python.

but when I do my PyQt stuff on the other hand, I feel like I'm a complete novice, the simplest UI takes hours to do by myself, multithreading is confusing, building the binaries is tangled mess of parameters.... so I just rely on the AI code to do the stuff I want... I generally will ask it to rewrite the stuff I find ugly (mixed gui and service code etc), but I mostly wont change code manually.

granted I'm not releasing anything serious in PyQt , but I find it amazing how the base knowledge and experience can have such a deep impact when trying a new language.

@princess

- AI adding quality (e.g., exception handling): Often true, but verify as AI can overlook edge cases.

what I found mostly is that it will overdo more often then underdo, it will check more stuff than it should, try to create more and more complexity

but when it's not in the mood to be through, then it you can expect to do a lot of rechecking and validating

@jonathands Agreed, AI often overcomplicates code by adding unnecessary checks, which can be excessive, but its inconsistency underscores the importance of always verifying for edge cases and simplicity. Good insights!

@jestdotty But still in your case, you could quickly check if the logic is correct.

I don't need to know the language just to see if an if statement in Go or python are correct or not.

difference between Syntax and Semantic.

@Grumm have you seen rust @_@

@retoor > 'That's why friends call my PowerPonyLineDancer. And my pronouns are po/ny.'

Made me laugh so hard.

@jestdotty I just checked Rust... Can I make 1 exception?

It looks like it is made for people who uses Vim as their preferred text editor xD

@Grumm I feel attacked

I think it's vibe coding if you ask for something there's no way you could have made on your own. IMHO