Yeah same. I make loads of little things to bodge my own problems but would never be moronic enough to try and capitalise on something that took 60mins to make.

I would guess that the key difference is that vibe coded apps can get to a more or less working state a lot quicker, while other apps are likely to be abandoned before it’s done.

Though in either case I’d always be careful with new projects. If it’s just a single guy that’s been working on something for less than a year and only have a handful of GitHub stars, I probably wouldn’t install it.

Also it's again the false sense of security pf "if you don't use vibed apps you'll be fine", making people forget basic security procedures.

I, for instance, had a service vulnerable and discontinued without noticing for months. It was something 100% made before LLM was a thing. Still had unpatched vulnerabilities and the project was abandoned. It was my fault for not checking more often is the services I host are safe or not.

but without the actual will and motivation to keep supporting that software to pump out software and publish it.

TBH, most software will never be used my many so needs no support. Also, I think lack of long-term support is not the same kind of problem. It used to be any more. Back in the day when the original author dropped support it was a major investment to get someone else up to speed. Now fixes and enhancements can be done by LLMs as well, given a somehwat competent software developer.

But in general: The newer the project and the more bells and whistles it has, the less I personally would want to make it an essential piece of my workflow.

I agree that people cannot vibe code well unless they are a developer. Knowing the difference between slop and using a tool to automate bulk writing code is crucial at the current state. And I don’t ever know if it’ll get better because you need to know why you want to build something someway.

Usually these tools are very basic.

If you read this community in the last weeks you'd know that slopcoders don't stop at basic projects.

I don't disagree necessarily, but they shouldn't be uploading / sharing one-off projects they don't intent to maintain.

On the flip side, if you’re vibe coding an app you should seriously consider whether it’s something you want to open source or make available publicly. There’s a social contract that comes with that.

This is the attitude of an existing programmer who is using these tools. What I’ve found on here is a specific pattern that keeps repeating:

1. A post is sharing/advertising a project. The poster is two hours old.
2. The poster is extremely coy about how their project was made despite obvious slop in the post body. They’re a bit clueless about anything that looks like a social contract that comes with that and think there’s something strange or accusatory/interrogatory when people ask questions they think are too difficult or technical
3. Some Lemmy users have generally polite but fundamental critiques and questions the poster can’t answer or thinks must be gotchas
4. The poster has a crash out about us all being mean/unappeasable/anti-AI/luddites/Linux users/godless commies and is usually the only one downvoting comments, even ones that read like genuinely interested, though cautious
5. The post and account are deleted

There’s a clear disconnect. You’re talking about the homelab community which is a bit different but I specifically remember someone making an accessible Android UI and being extremely frustrated at people asking for the entire code to be released, and at people saying there’s not enough features there for that poster to be looping in advertisements on a fucking home page UI.

I get the impression that primarily-slop coders on some level think they’re doing programming, because of how you can get functional prototypes of code that is way above what a total beginner can write on their own. They think having code that compiles (whatever it’s usually Python there’s no compiling) means the hard part is over. They don’t seem to understand that the questions and concerns about vibe coding aren’t moral complaints but genuine concerns about liability, running code even the author doesn’t understand, and a complete cluelessness about what they should be doing to evaluate the code besides prompting it to be “good with no mistakes”.

That Android UI project seemed like a little thing a few people could install on their grandparents’ phones. It’s normal for the author not to understand every little thing. But being totally clueless and being offended at the suggestion, being entitled to put ads in it to get 0.0016 USD per year per grandma in exchange for taking up a quarter of her screen forever, not understanding why this looks scummy, why refusing to release 60% of the code looks scummy, why half the questions are being asked at all.

Again this would not be a problem if this wasn’t now expected for a significant portion of any projects you find online. A lot of projects are the first genuine effort of someone out there and they’re not perfect but they didn’t feel like the unceremonious implosion of the entire philosophical concept of personal computing.

And I’m fucking shit at writing good code and I’m pissed.

That is so accurate. I have a couple of LLM-coded applications running, either because a solution wasn't available, or existing solutions were beyond the scope of what I need, and would idle at up to 1 GB of RAM instead of 10 MB. In situations like these, being able to get a quick solution thrown together is such a boon.

Are there any obvious signs of it being vibe coded that I'm missing?

In my experience, projects not being very active, especially small ones by a single person, isn't anything new that has much to do with LLMs, it was always that way for hobby projects. And it was inactive for only about a month now, with the author replying within one day before that. I have a few hobby projects myself and don't reserve time every month to work on them or check on their repos.