It's enough - vibecoding tag crossed from useless to harmful

272 points by viraptor


The vibecoding tag has been getting more and more useless for a while now. It lost the original meaning as the culture of software engineering with LLMs matured a bit. It got silly when posts talking about LLMs in general got tagged. It got useless when posts even mentioning some project created with LLMs in passing got tagged. Now it actually got harmful to the community when tagging posts turns away very valuable members https://lobste.rs/c/vecuxj

I sighed and moved on for a while now as almost everything gets tagged - you can skip a word. But now it not only carries no signal whatsoever, it turns away people creating original technical content - which is what I assume anti-vibecoding people would actually like to see more of.

Please split it or kill it. But we'd be better off without what exists today.

Added: To be clear, I totally support people filtering out llm-generated or llm-centric posts. But right now everyone loses. And every day we lose a little bit more. Whether it's an original, interesting article that turns out to be nth-degree related to llms and filtered out, or a community member annoyed by this recurring problem and leaving us with even fewer actual non-llm-centric entries.

hyperpape

I agree with the reasons the OP stated, but what bothers me even more is how the discussion on lobsters has degraded.

So often, the top voted comments on a post are low-effort, anti-intellectual labeling of things as vibecoding or slop. I've used the word "slop" in the past to describe low effort work, I think it could be a useful word. But when we have a heckler's chorus insisting that anything that uses agents is slop getting consistently upvoted, that's anti-intellectual (https://lobste.rs/c/rqmtmc).

Lobsters has gotten much more content free, and I don't think the problem is people posting coding projects built with AI, it is people grandstanding about how much they hate slop, over and over again.

I blocked lobsters on my work laptop with /etc/hosts, and I wonder if I should block it on my home machine as well.