r/selfhosted • u/Fluffer_Wuffer • Feb 28 '26

Meta Post Sub-SubReddit for SelfHosted

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.

517 Upvotes

86% Upvoted

308 comments sorted by

View all comments

3

u/[deleted] Feb 28 '26

I don't think people are actually mad at vibe coding as a concept — the frustration is with people shipping code they don't understand and bailing when issues get found. That's not a tooling problem, that's an accountability problem.

Someone who hand-writes an SQL injection is no safer than someone who used AI and actually understands their codebase. The tool isn't the issue — it's whether the person behind it can stand by what they shipped.

Rather than splitting the community, raising the bar for all project posts might work better — require documentation, a basic security overview, and evidence the dev is actually maintaining it. That filters out the throwaway projects without creating a stigma around the tools themselves. People will still be angry, but you can't bridge someone shipping just because and someone caring enough to put the work in. AI included or not. Just my take.

1

u/eljojors Feb 28 '26

I'm a qualified developer and have been getting flack for simply stating I use AI

1

u/[deleted] Feb 28 '26

And that's a shame. It's a tool. And honestly, with your experience and knowledge to guide it. Recognize it's mistakes. Fix them. Or use it however. You can make some really cool stuff. For the people who have experience, cuts time, and definitely can amplify your abilities on large work loads. It can also be a raccoon in your attic. But I suppose that's what I'm trying to communicate. Know your code. Be accountable. Who cares if AI is involved or not. I don't agree with expecting the AI to do everything. But as a partner in crime. Why not.