What's wrong with vibe coding?

I prefer Vibe Prompting™ tbqhwy familia.

>>106103693 (OP)
I prefer vibe boning your mom

>>106103693 (OP)
Nothing. It is the future of programming. Anyone who doesn't vibe-code today is already hopelessly behind and will be living on the streets within six months.

>>106103693 (OP)
There's nothing wrong with it but you really need to understand code to use it properly because AI makes baffling decisions.

>>106103693 (OP)
Dishonor on you
Dishonor on your cow
Fuck your shit thread
And fuck you

are there vibecoding bootcamps yet?

>>106104064
Unemployed hands typed this

>>106103693 (OP)
It lets retard nocoders like me fix scripts and shitty old software no one uses, all for personal use only. I don't share because people with an IQ higher than 90 can solve and fix them. Mine is 86 :3

what do you do when your vibe code has an error and you can't actually program

>>106103693 (OP)
why is vibe coding all webshit instead of something truly useful? Like make a good fem suite for linux if its so powerful or write a adapter for elmer if writing one from scratch is too hard. But either case the "AI" fails.

>>106103693 (OP)
For me, it's vibe gooning.

>>106104457
vibe coding doesn't necessarily imply not knowing how to program

>>106105619
the dream of vibe coding is to render programming knowledge obsolete
it is to programming what the factory floor was to furniture
you are missing the point if you actually try to learn programming via vibe coding

>>106104457
>what do you do when your vibe code has an error and you can't actually program
"Chatgpt theres an error somewhere here can you tell me what it is"
it's as simple as that.

lol that address

i love how it's impossible without any more context to know if he's being genuine or not. either this is an intentional dig at "vibe coding" or an unintentional dig at the intelligence level of "vibe coders"

>>106105776
>you are missing the point if you actually try to learn programming via vibe coding
obviously you have to first learn to do it by hand, just like with maths.
But the hypothetical use case today is to have a good programmer shit something out a bit quicker while having to think less, which allows him to be productive even during times his mind isn't up to complex thinking, i.e. while tired.
I'm not sure it works because I haven't tried it, but I can't dismiss this out of hand just because nocoders and pajeets ruin the concept.

If its so powerful some retard can learn it in 5 mins then I will take 5 mins to learn it down the road until then just gonna sperg out on c++/graphics and sharpen the blade.

>>106103693 (OP)
https://youtube.com/watch?v=_2C2CNmK7dQ

>>106103693 (OP)
>pic
i suspect it is a joke because i laughed
t. vibecoder

>>106105776
programming is mostly monkey work where you're typing out an idea that takes 60 seconds to think about but an hour to write completely, oh and it's basically all memorization too

>>106107731
>t. webshitter

>>106106059
That's the problem, "vibe coding" is a slur for someone that has AI do all their code without understanding it.

I do embedded C professionally. GPT writes half my shit, but I still verify and debug. gpt is very good at small discrete tasks, pretty bad at big-picture interconnected things. So ai does my easy time-wasting bullshit, I focus on the weird shit and getting everything to play nicely together, and I'm probably 40% faster than before.

>>106103693 (OP)
I thought vibe coding was coding without a definitive structure... What does it really mean because this tweet implies a different thing

>>106110284
>"vibe coding" is a slur
And that's the funniest part. You take someone who legitimately use AI as a retarded intern (while reviewing throughoutly since it's your name on the signature, not the intern's), and take a retarded internet who think he can use AI to be the engineer. And you just lump them both together to watch the infighting while you're on the corner LOLing you ass off.

It doesn't matter whether you use AI or not, whether you vibe code or not. Whether you use it as an insult or whether you're trying to own the term. You just pour gasoline on the flames and laugh.

>>106110662
It means heavily relying on AI to code for you and not really checking it.

>>106104457
im practically a no-coder in the eyes of /g/
i say that i have broken past hurdles more often using AI than trying ot learn how something works, then there are those edge cases where you actually need to learn how it works, you do so and continue vibe coding.

wtb today gemini went on an infinite buckle on me, it printed 4k lines and had to stop it from burning down googles servers so close.

>>106110779
They should rename it to jeet coding, vibe coding has a cool connotation to it

>>106110662

>>106104064
This. But you should still know how to code so you can catch glaring issues as they happen or debug anything the AI's not catching.
>>106104457
You describe how its not behaving as expected, and retry your last prompt. Or if you really can't fix it, you scrap it and start again. Vibe coding this way when you don't know how to program at all is really only useful for one-off problems you need a script to solve. It's not going to be feasible for building some working product to go out to production.
I do this when I need python or vb scripts, because I never learned these things. If I had to, I could probably debug them, but they're not languages I can just scan and catch the issue without a lot of googling.
>>106104118
/thread

>>106103693 (OP)
>>106111255
How behind am I for not using cursor?
I use VS Code without ai when I'm actually coding, then if I need a script that's more than light amounts of thinking, I use chatGPT.
I found both Cursor and copilot to be clunky and distracting.
75% of what I do is literally just HTML/CSS. Sometimes php.