this post was submitted on 27 Feb 2026
213 points (98.6% liked)

Programmer Humor

30063 readers
1735 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
213
AI slop repository with 8k stars on Github that doesn't even compile (github.com)
submitted 1 day ago by cm0002@infosec.pub to c/programmer_humor@programming.dev
44 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] kadu@scribe.disroot.org 60 points 1 day ago (4 children)

I have a visceral "AI" sensor that triggers when I see these:

"Rust Implementation (v2)"

"Performance Benchmarks (Validated)"

Human beings don't self-validate explicitly like that. AI loves doing it.

You generate code, there's a bug, you ask for a fix, your AI of choise will always output with:

*** Fix build issue ***

*** End fix ***

and then call it "Version 2 (Validated)".

Sometimes it's more subtle, but you can feel it, it loves adding "confirmed", "working", "validated".

[–] FishFace@piefed.social 36 points 1 day ago (1 children)

My sensor is much simpler. If I see emoji in headings or bulleted lists, I assume it's shit. It might be AI slop, or it might just be kids getting overexcited with the little pictures, but both deserve suspicion and scrutiny.

If a bunch of the emoji don't even make sense it can get in the bin.

[–] eskuero@lemmy.fromshado.ws 29 points 1 day ago (1 children)

This comment is so true 🚀🚀🚀

[–] over_clox@lemmy.world 41 points 1 day ago

This comment has been confirmed and validated by an actual human being 👍

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

I have a project with a bunch of compose files that define the services I self host. I "deploy" the project by sshing into my server and doing "git pull" which means I'm often making changes that don't get tested before committing to source control. As a result I have long chains of commits like:

  • refactor the sproingy widget
  • refactor the sproingy widget v2
  • refactor the sproingy widget working
  • maybe the sproingy widget works this time?
  • ok finally found the issue with refactor sproingy widget
  • fix formatting of sproingy widget

And now I'm wondering if I've been an llm this whole time

[–] housedogpartyfavor@lemmy.zip 7 points 18 hours ago

No the AI would have called it fixed, “production-ready,” committed, and pushed after the first refactor.

[–] exu@feditown.com 6 points 23 hours ago (1 children)

Make your changes in a new branch and rebase/squash when you push it to main.

[–] IronKrill@lemmy.ca 4 points 20 hours ago

This also means modifying your git pull command to pull the correct branch. A small change perhaps, but may be harder than just committing to main lol.

I had a similar problem with GitHub actions, it was hard to test without messing up the main repo history.

[–] Neptr@lemmy.blahaj.zone 1 points 1 day ago

Also the repo image