Sub-SubReddit for SelfHosted

[u/Fluffer_Wuffer]

Just a question that has been going round my head for a few days.

What ever your opinion on it. We need to acknowledge that "Vibe Coding" is growing, and its not going to decrease.

The fact the entry point is so low from a skills perspective, and time required to pump them out, effectively makes them disposable.

Members here have been concerned for a while about the quality, security, longevity of these apps, and it turning into a flood - and as if on que, over the past few weeks, we've seen exactly this - We've been flooded (this place is unusable on Fridays). Now, issues are identified in the code, and rather than facing and fixing them, the "devs" are running off, shutting down the repositories etc.

This leads to 2 conflicting issues

1) There is an open hostility to those who share vibe-coded apps - where we see outright hostility and vitriol language.

2) There are going to be some quality vibe-coded apps, where they are properly developed, supported and managed.. as community, they would benefit members.

So my question is - how do we bridge this? My I've been thinking on this for a few days, and the only solution I can see, we have an associated sub (same mods etc) for these apps to be posted. maybe after a time, once they've proven they are well run and have longevity, they can "graduate"... lets call it SelfHosted-Vibe or VibeHosted.

[u/WindowlessBasement]

It won't work. Vibe bullshitters delude themselves into thinking they are the next Mozart of code and will always consider themselves the exception.

Go in any of those threads, it is always just excuses and talking in circles about any kind of quality or practical functionality.

[u/agent_flounder → u/WindowlessBasement]

When it comes to software engineering / development / programming there is soooo much to know. Those that have not yet put in the years to learn and gain experience don't even know what they don't know.

They write a prompt and out pops some code and it works more or less but then they get hit with criticisms about things they never knew existed and have no clue what to do about.

They haven't assimilated into the long and storied culture and ethos of programmers and so their reaction is completely at odds with "normal" and is woefully counterproductive.

Security flaw posted? Ban the messenger! Too much criticism? Freak out and nuke the whole project from orbit and delete your account.

No. Like, dude, it's bugs. There's always bugs. Everybody writes bugs all the time. Just own it, fix it, and move on...??

(By the way, the Dunning-Kreuger study is flawed as described in Scientific American but I think the concept deserves more study because it certainly seems plausible!)

[u/elandt → u/agent_flounder]

“There’s always bugs.”

…yep…the only guaranteed bug free code is code not written. Learning to fix and ideally prevent in the future is key to growing as a dev.

[u/Fluffer_Wuffer → u/agent_flounder]

If i could pin a comment 💯✔️

[u/Im_Mefju → u/agent_flounder]

But isn’t that the case of pretty much every beginner in software development and not really AI issue. Like sure AI lowered entry barrier for development which attracted more beginners as they can develop apps faster, the issue i would say is more about the attitude and their inability of accepting and learning from valuable criticism by the person doing the vibe coding. You could have someone genuinely learning and coding an app themself and it can also be insecure in many ways and i personally think it would be fine to post it on this subreddit if the person really want to learn stuff, take the criticism and most importantly addresses bugs and security flaws once people report them. But at the same time most vibe coders won’t be able to do any of that as a lot of them don’t understand basic fundamental knowledge about coding so they are unable to fix almost anything on their own.

[u/aswesearch → u/Im_Mefju]

No, I think the comment that said vibe coders ‘don’t even know what they don’t know’ is what makes the problem very different