this post was submitted on 27 Mar 2026
165 points (88.4% liked)

Fuck AI

6540 readers
821 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
 

It has to be pure ignorance.

I only have used my works stupid llm tool a few times (hey, I have to give it a chance and actually try it before I form opinions)

Holy shit it's bad. Every single time I use it I waste hours. Even simple tasks, it gets details wrong. I correct it constantly. Then I come back a couple months later, open the same module to do the same task, it gets it wrong again.

These aren't even tools. They're just shit. An idiot intern is better.

Its so angering people think this trash is good. Get ready for a lot of buildings and bridges to collapse because of young engineers trusting a slop machine to be accurate on details. We will look back on this as the worst era in computing.

you are viewing a single comment's thread
view the rest of the comments
[–] AdamBomb 3 points 1 day ago (2 children)

Yeah, don’t generate code with it. Treat it like StackOverflow. It does pretty good at that.

[–] BlameTheAntifa@lemmy.world 5 points 1 day ago

This is the only way I use it, and I do it grudgingly only because AI has ironically also ruined the web and web search. It’s also a last resort for when Kagi isn’t helping.

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

Unfortunately for me it’s a kpi so I need to figure out how to do something useful with it.

LLM is good for

  • temporary scripts like to export data
  • boilerplate for new code
  • simple or repetitious code like unit tests

But just in time for my performance review, I spent a week ignoring my work to set and tweak rule sets. Now it can be noticeably more useful

  • set context so it understands your code better. No more stupid results like switching languages, making up a new test framework, or randomly use a different mocking tool
  • create actions. I’m very happy with a code refactoring ruleset I created. It successfully finds refactoring opportunities (matches cyclonatic complexity hotspots) and recommends approaches and is really good at presenting recommendations so I can understand and accept or reject. I tweaked it until it no longer suggests stupid crap, although I really haven’t been able to use much of the code it tries.
  • establish workflow. Still in progress but a ruleset to understand how we use our ticketing system, conventions for commit messages , etc. if I can get it to the point of trusting it, it should automate some of the source control actions and work tracking actions
[–] GrindingGears@lemmy.ca 1 points 1 day ago

Just literally make something up and get it to lie about something. This is literally the land of make belief at this point, all this KPI shit. Don't stress about it. Execs want slop, give em slop.

[–] AdamBomb 2 points 1 day ago

I agree with all that, especially if your performance is being measured by your use of LLMs. Those are cases where I find the code generation to be ok and doesn’t create comprehension debt.