debugging a colleague's bash script written by copilot.

fun
/s

When I told John our newest colleague “I understand your frustration but you need to calm down because collaboration is key”

John:
Okay okay okay, I get it. Collaboration is key and all, but these meetings freaking killing me. We need a better balance, where we can have effective meetings that actually drive progress without sacrificing our precious coding mojo.

At the end of the day, I just wanna do what I’m f*ckin paid for. But these damn meetings are killing my vibe, and it's downright frustrating. Can't we just get back to the good ol' days of actually getting sh*t done!

{Bro is in for a long ride}

Oh my goooooooooood vibe coding is sooo bad

Holy fucking shit I'm actually losing my mind

Cursor is nothing but a glorified slop generator. It just fucking yaps and yaps and it generates shit upon shit. Yet NOTHING works properly

It all looks impressive but its all a shallow house of cards of bullshit

To be fair, I'm trying to make it write a simple compiler with an x86 JIT backend. Absolutely not a simple task, but come oonnnnnnn. It just goes in circles, over and over and over

It's exactly as I imagined. Just like ChatGPT, if it failed 2 times, it will never recover and you should just start a new conversation to clear the poisoned context. For a half hour I've been trying to get to compile a program which prints hello world. It just can't do it. No matter what, the compiled program just always returns 42 and nothing else (or segfaults)

It's just fucking AI slop. It LOOKS impressive until you actually go a bit deeper and you realize its all vapid bullshit

I fully expect to be roasted here, but I, for one, welcome our new vibe coding AI overlords.

I've never been good at coding for one major reason: I cannot commit to memory or manage to effectively use enormous sets of commands, principles, techniques, frameworks, etc., that are often required for this work. I've always been a huge source of frustration for team members who have that innate ability, in that I slow them down, make lots of mistakes, and generally don't know what I'm doing in the context of everything available to me to use. Especially in comparison to them. The only good ability I seem to have is picking through code others wrote, updating it, debugging it, and generally comparing it to best practices to either ask them to fix it or figure out a way to get it done myself. But it takes me a long time, and it's super frustrating.

"Vibe coding" has been world-changing for me in that regard. I know. It's not "pure coding". I know. It's "stealing our jobs". I know. "It's making us all dumb and dependent".

I don't care. I'm trading that for FINALLY being able to realize the vision of all the projects my right brain WANTED to do for so long, but that I never tried because I knew my limited left brain couldn't manage it. I knew the UI and the requirements, but I just couldn't get started. Or, if I got started, I couldn't figure out what to do next. I knew how to explain it, but it would take me many more hours than necessary to write the first working class and functions.

I'm in this to make money. I'll leave the "coding poetry" to the purists. I need an MVP, then a v1, then a v10+ as soon as I can possibly get them done, so then I can get the software to market before some other competitor.

If that makes me some kind of terrible person or shit coder who's "ruining everything" (really?), so be it. I'm due to retire in the next 5-7 years. If I can make that happen earlier with more sold software, all the better.

Project manager wants that we write a full app by only vibe coding and he is enforcing this...

Gotta say, this is one of the most unsatisfying projects so far...

I've been vibe coding not knowing that it was called that until yesterday. I always give up before I reach anything interesting because I get about 4 or 5 good responses before it starts forgetting things and breaking already working code. And it's not even that complex of an idea.

There is no way people are coming up with whole applications with any level of complexity with these things.

Your code is 250 lines. My prompt is 250 lines.

We're not the same.

I really start to love this way of programming. Think upfront, don't let the LLM make any decisions. Think everything trough up front.

Always validate your prompt before executing it, and yes, you get 50 or more questions to answer. You answer them and ask him to update the prompt. In the end you have a master piece and claude 4.1 OPUS will completely render it for you at once. It will generate HUGE applications if you specify it well up front. But i always let it make one file applications. Big tip. When it's perfect, you can always do a split by another prompt. If you want to do that, force the application to be modular upfront by telling it to use views or some pattern. Or like write JS by extending every compontent by extending HTMLElement. Every component is isolated. That kind of stuff.

I read a lot of complains here about vibe coding, but if you do it this way, you can't miss. To spec the full prompt, i use gpt.

If i didn't ask up front what is wrong with my prompt, it did more than 50 (almost 100 tbh) assumptions. And yeah, in that scenario you'll never get the application that you want. It's literally shit in, shit out. Cool stuff in, cool stuff out.

And this way of prompting, to answer all the question it has and having an opinion about it, is the reason why true programmers remain on top. As newbie, you can almost forget this method.

Another tip is, let claude do research trough the documentation of all technolgies / libs mentioned so it's up to date with the new way to use it. It will perform 400+ web requests to figure out how to use them.

Vibing not for the lazy people. Take time, pays off.

Vibe coding should be punished of 7 years in jail and a 10000€ fine. Doing so while screen sharing should add 2 years and 5000€ on top.

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?

I watched a YouTuber that had thousand hours of experience I'm vibing and was like, wow, he sucks. My way is like hundred times more effective. How he works would result in many hours for sure.

Do you guys have vibe coding tips/tricks you swear by to get good results?

Vibe coding: imagine that you're "vibe cooking". You toss some spices in a "smart pan" and its supposed to add staples like flour and rice and water automatically, then cook the results.
Things get so easy when you're not the one supposed to eat the grub/sludge/muck that comes out.

Hearing DHH call vibe coding "empty calories" is

👏 on 👏 fucking 👏 point 👏

I realized that my mood swings based on how my gf behaves. She is one of the few triggers

If she is sad depressed angry or disrespectful towards me i am no longer in a positive mood, it kills the whole vibe. On the contrary if she is happy acts feminine behaves normally and is respectful towards me i also become happy and in a better mood

Bad mood does not stop me from doing my work, but depending on how terribly bad it becomes, it may or may not impact my coding and work life. Since the main and central tool for coding is my brain and mental state, not physical muscles, Once the central part of anyone's tool (thats used to get the job done) is attacked or threatened, it weakens the person's ability to perform as good as they have been, or worse, completely blocks them off from performing well

This is one of my biggest fears; Anyone who's capable, intentionally or not, of weakening the central part of my tool for work (in this case mind and mental state), begins to gain power and leverage over me (hold on this is actually a brilliant idea to have in mind, a malicious way to exploit and leverage the target victim is by attacking the central tool they use to get the work done)

However i am a mentally strong person (due to way too much trauma from school, solving extreme difficulty coding problems, hoes and financial struggles), but it does not help if i am attached to a person who i have feelings towards, a person who became the second half of me, "the better half". It is difficult to reject or all of a sudden stop loving the person who you loved for years or months. Such person can more easily attack my central tool

My question is--does anyone know how to protect the central tool from anyone being able to exploit or weaken it? For example if my gfs bad behavior puts me in a bad mood, how to prevent that from happening? How do i not care? Or how do i care but still not let it affect my mood in a negative light? If that makes sense

Vibe Coding is the start of the end of days

What do you think?

🚀 Vibe coding be like:
👉 First 30 mins: "I don’t fully get what’s happening here…" 🤔
👉 Next hour: magically works 💻✨
👉 Then: you try one tiny change → AI confused → you confused → now you are reverse engineering your own code 😅
But for real… AI is doing A LOT right now. The tricky part is knowing where to draw the line, discipline is the only guardrail. Sometimes you don’t even notice when you’ve crossed it.

I know vibe coding is a thing now, but I do hear a lot of people talking about how the AI can get off track and make some pretty bad mistakes. I think (for me at least) the takeaway from that is use it, but don't ask it to do anything that you couldn't do yourself.

Web flow vs vibe coding, what's worse?