this post was submitted on 31 Jul 2026
156 points (99.4% liked)

Fuck AI

7807 readers
807 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
 

cross-posted from: https://lemmy.blahaj.zone/post/46091883

Though nobody expected it in the first place, AI is not perfect and can make mistakes (obviously 🙄) What’s your experience with this? I’d love to hear about it.

you are viewing a single comment's thread
view the rest of the comments
[–] panda_abyss@lemmy.ca 7 points 2 days ago* (last edited 2 days ago)

This ticket was a small chore rather than critical bug. Just hygiene of keeping ids internal.

Literally all they needed to do was switch user.id to user.username in the result object.

The user fields are always in context because they’re stored on the session, and even if they weren’t, there was a fetch on users they could be trivially added to a few lines up in the method. Even a second query in the method wouldn’t be a big deal, as it would add a couple ms at most.

We get username from another service, so it’s already clean. The AI seems to have not understood this and went insanely defensive.

Way worse code than the original, though I’m sure it probably passes all the new tests.

Edit: this is what reading the PR felt like https://www.youtube.com/watch?v=y8OnoxKotPQ