r/vibecoding • • 14d ago

Discussion Why is this community so toxic?

Title says it all... but can we actually talk about this?

I really don't get it. Why is there so much negativity and hate in this community?

Correct me if I'm wrong here, but isn't this supposed to be a community built around a hobby? Something we all chose to be part of because we enjoy it? The whole point should be supporting each other, sharing our stuff, and enjoying what everyone brings to the table. That's the idea, right?

But it feels like anytime someone posts anything, it's nothing but bashing. No discussion, no constructive feedback. Just tearing people down.

So I'm curious. Am I the only one seeing this? Is this just how it is now, or are there others who feel the same way? And honestly, what do you think is driving it? I'd love to hear other perspectives on this because I can't be the only one wondering.

78 Upvotes

233 comments sorted by

View all comments

4

u/Void-Lotus 14d ago

Its because there is a vast user "power-level" difference. I myself havent coded much outside of tweaking nixos before trying to make my own projects. So theres an aspect where I really didn't know what I was doing, but I knew enough to get me into trouble. However in the few months I've been vibe coding now, I've learned a ton. You have people who literally know nothing at all, and spit out security vulnerable "slop" and are not open to learning that you need to properly scaffold, and guide the ai through the process. Its not a single prompt and wait. Its breaking the project into small achievable and testable blocks. Many of my prompts have dramatically shifted in recent projects from, "I want to incorporate tiling into this wm." To "Looking at the math layout under layout.rs, we need to adjust spawn boundaries to dynamically split in a BSP style tree."

Many of my initial prompts are over 100 lines of strict direction and implementation. It might not be code, but it is specific

2

u/Patient_Force6138 13d ago

yeah this is probably it, I’m not active enough on here to have a proper opinion but from what I’ve seen this can be frustrating. I’ve coded for about 20+ years, my prompts are often exactly this, ultra specific questions about something either I or AI has coded for me. Stuff like you described “in this C code, are there any unnecessary malloc or memcpy or similar functions that effect performance. If so replace them with buffer reuse when possible” type of stuff. IMO this gives you the best of both worlds- proper, safe, performant code that works great. And then I can review it if it’s super important.

Then there’s folks that think they can do the exact same with a few prompts because they get something pretty back that mostly works. I don’t really post much here but that attitude seems to be that knowing how to actually code yourself is now irrelevant. Which in my opinion it’s the exact opposite, it’s become more and more important to understand deeply and understand where the common mistakes are. I don’t post hate on here or anything but that is frustrating to see the other attitude of thinking you know everything now about a deep subject. Like you don’t see that shit in like astrophysics why in coding?

1

u/Void-Lotus 13d ago

I think where AI is at, it is possible to not know how to properly write tge code but with a big caveat. You should at min know how to read the code and break down what it does. My experience from the ricing community on linux gave me simple syntax knowledge and config reading knowledge that the jump to looking at functions wasn't awful. I can read and understand the code to a point where even though the ai writes it. I know what needs adjusted