this post was submitted on 23 Oct 2026
304 points (98.7% liked)
Fuck AI
8638 readers
1564 users here now
"We did it, Patrick! We made a technological breakthrough!"
A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.
AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.
Rules:
- Relevant posts only.
- No bigotry.
- This isn't a place to talk about the cons and (supposed) pros of AI for different use cases. This is /c/fuck_ai .
- Especially no AI advocacy.
- Don't make any posts that are just AI content with no context unless the point of your post is obvious from content. (Don't just post slop advertisements or slop political cartoons. At least make your point about it clear so we know you aren't just trolling.)
- Venting is part of the purpose of this community, but don't aim frustration or accusations at other users.
- These rules are a living document that may change in the future.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That’s unfortunate. But less unfortunate than it could be.
The problem with pure vibecoding is that it can get really flashy results up front, just enough to impress and get green lights. But it’s completely unsustainable outside the simplest projects. At some point, vibecoded stuff gets issues, or one realizes certain features actually aren’t working, and no one can fix them.
In other words, it’s great that QA is already catching the issues. Because they could have quite possibly vibecoded something functional, passed through QA, and ended your separate effort, only for it to collapse later.
Note that I am strictly talking vibecoding, though. I know it’s not a popular opinion in this sub, but more mundane LLM “chore automation” is far more practical.