this post was submitted on 11 Jun 2026
98 points (99.0% liked)

Fuck AI

7069 readers
1821 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.

founded 2 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] victorz@lemmy.world 28 points 1 day ago* (last edited 22 hours ago) (4 children)

Actual comment proving it's bullshit: https://github.com/rhinstaller/anaconda/pull/7074#issuecomment-4556782893

But the PR is still merged. What does that mean. They just accepted it anyway? 😒

Edit: it was reverted, I hear ya πŸ™πŸ€Ÿ

[–] jj4211@lemmy.world 3 points 20 hours ago (1 children)

Yeah, I was reading the comment before and anyone with a vague awareness of this stuff should have called bullshit immediately.

Preserving the argument seemed an innocuous enough change though, so I could see why it was accepted, but the explanation was bafflingly stupid.

But people who don't know eat it up. Sounded possible (until they claimed the system crashed and could not log the error, despite a log entry belt there that they ostensibly cite as the issue..).

[–] victorz@lemmy.world 4 points 19 hours ago (2 children)

I just don't understand the workflow with these people.

You know how people say "don't run a command you are given or find online unless you know exactly what it does"?

Why would anyone accept/merge a PR from an LLM unless they knew what the consequences were, or verified its claims. I just will never get this trust in LLMs, given I know even vaguely how they work.

[–] LePoisson@lemmy.world 1 points 12 hours ago

I just will never get this trust in LLMs, given I know even vaguely how they work.

That's probably a good stance to have. I just had an AI hallucinate the hell out of an answer and tell me 3 different times the wrong thing. I took a step back, started a new chat, and changed my question to be less specific and more general and the very first thing it spit back was bang on right.

This is just in regards to figuring some shit out in a video game, it's alarming to me how much trust people are putting into these LLMs and the AI tech. Just a huge bubble that's going to wreck our markets when it bursts. Eventually venture capitalists (ew) do want a return on investment - and that just is not going to happen.

I think the great AI bubble burst, whenever that happens in the next 1 to 3 years, will make the dot com crash and 2008 housing crash look like peanuts and that's gonna be real bad for lots of people.

But hey, the earth keeps on spinning, we're just along for the ride.*

*Unless you're a filthy rich member of the borgeousie, in which case, for the love of God have your tech buddies reign this shit in.

[–] jj4211@lemmy.world 1 points 13 hours ago (1 children)

Well, in this case, the actual change is pointless, but also relatively harmless. If the user puts "split_lock_detect=" during install, then it just carries it forward into the installed environment.

It's frankly a bit weird that they assume a kernel argument during install would not carry over, except in select circumstances. I get it for parameters like "here's a kickstart file" or "here's the net configuration to boot with", which would be filtered out via a blacklist, but they have a whitelist and assume most parameters should be ignored.

But anyway, I can see someone looking at the code change, not recognizing why someone would want that argument, but shrug and say "sure, simple enough, it won't impact the vast majority of people and those that bother for whatever reason will just see it carried forward".

[–] victorz@lemmy.world 1 points 12 hours ago (1 children)

But clearly it wasn't something anyone wanted as it was later reverted, and not kept in because it was supposedly harmless.

I get what you're saying though. I'm just glad someone in those comments actually analyzed the situation instead of putting their trust in the charismatic LLM. Those people still exist!

[–] jj4211@lemmy.world 1 points 11 hours ago

Funny part is that if it just stated "sometimes the user needs this argument, and if they need this argument for install they will need it to boot", they might have shrugged and let it slide. In trying to overexplain, it betrayed that there was no actual understanding behind it.

[–] Azzu@leminal.space 21 points 1 day ago* (last edited 1 day ago) (1 children)

That's what happens when you don't actually understand the change and just listen to whoever is posting it. The disingenuous thing about LLMs is that they present their hallucinations with full confidence in a charismatic way. No matter the source, that is how anyone can mislead other humans, we're just so extremely susceptible to it.

[–] victorz@lemmy.world 3 points 1 day ago

we're just so extremely susceptible to it.

Judging by the leaders of the world throughout history β€” yes we are indeed. And it's so sad.

[–] unrulyhillperson@piefed.social 13 points 1 day ago* (last edited 1 day ago) (1 children)

Looks like it was reverted shortly after the comment you posted.

[–] one_old_coder@piefed.social 13 points 1 day ago (13 children)

I didn't notice that. The fact that Redhat is merging random crap is scary.

[–] jj4211@lemmy.world 2 points 13 hours ago

Well, this case the actual little 'code change' is pointless, but harmless, so not so scary. The rationale is stupid because the purported root cause makes no sense against the behavior, but preserving a custom boot parameter added to install to also apply to the installed OS is pretty milquetoast.

load more comments (12 replies)
[–] jtrek@startrek.website 1 points 1 day ago

Looks like it was reverted later?

[–] Arghblarg@lemmy.ca 31 points 1 day ago (3 children)

I've recently had to begin dealing with this type of crap at my job in the past month, and it's infuriating.

Testers using LLMs to analyze logs, said LLMs cockily composing a multi-page 'bug report' stating the supposed cause, spewing a metric tonne of mostly irrelevant context and gaslighting with authoritative-sounding conclusions about the root cause of the issue; and since it sounds so damned confident in its verbose hallucinations, I have to waste precious time explaining to the test team and my manager why the report is mostly or entirely wrong.

Goddamn, I am so ready to retire. Let these "dark factory" advocates bury themselves in their models' slop. There will be a reckoning someday for this I swear; and if, someday, a company comes to me to clean up the mess "AI" has wrought, I will demand 3-4x my regular salary to clean it up, or, if I am financially content in retirement, I will simply tell them to go fuck themselves and lay in the bed they have made.

[–] jj4211@lemmy.world 1 points 20 hours ago

I'm with you, but so so far away from retiring.

Silver lining is that the company refuses to pay for more than included GitHub copilot tokens. They are currently in denial and saying folks can just use the cheap models to build management's dream of "native agentic workflows", but I fully expect them to have to face the reality that people will get fancy tab completion and the occasional prompt and that's it. I can deal with that volume.

But still after each model release I go to use it and save examples of it falling on its face. Because each time a new model launches management is convinced that the llms don't make mistakes anymore. If they just said it is getting better that would be one thing, but they are always convinced that new LLM was when all the issues were fixed.

Working on open source has been tougher, since other people have blown budget on making harder to understand bug reports and pull requests.

[–] criss_cross@lemmy.world 4 points 1 day ago* (last edited 1 day ago) (1 children)

My company loves having people shooting out vast amounts of PRs to other teams with surface level fixes to things we’ve been working on for months. You can tell none of them have been tested and only like 50% of them work. It’s infuriating.

[–] jj4211@lemmy.world 2 points 13 hours ago

Oh yeah, that reminds me of yesterday. There was a problem and I was asked to look together with a guy from another team. The other guy was spinning out and spouting all sorts of wild ass guesses about the behavior and talking and talking about why it might be happening and why it calls for a change that would have been massively a pain in the ass for the user, but in principle would solve the issue if implemented, and pressuring me to make those changes right that second.

I said just wait a moment, gave a patch that just simply fixed the problem, explained the actual root cause, why it was a very quick fix, and used the balance of the time to improve performance because the experience was slower than I liked, even if the customer had not complained about it (something took about 2 minutes that should have been near instant, but they just "assumed that's the way it is").

No AI involved whatsoever, but a very AI like behavior of spouting nonsense that sounds right and just shotgunning off some design in hopes of it doing something, no matter how messy.

Just an example of why AI is so "exciting" in the tech industry, so many are already used to just guessing without understanding and hoping it works.

[–] victorz@lemmy.world 6 points 1 day ago

tell them to go fuck themselves and lay in the bed they have made.

Wouldn't that be oh so satisfying. 🀀

[–] northernlights@lemmy.today 16 points 1 day ago

Wow what a massive waste of everybody's time.

load more comments
view more: next β€Ί