320
AI slop repository with 8k stars on Github that doesn't even compile (github.com)
submitted 6 months ago by to c/programmer_humor@programming.dev
66 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 91 points 6 months ago* (last edited 6 months ago) (6 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 choice 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".

  • permalink
  • fedilink
  • source
  • hideshow 12 child comments
    •
  • [–] 59 points 6 months ago (3 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 8 points 6 months ago (2 children)

    Ahhh idk, I saw a lot of genuine repos do emojis, at least for headings. Even before LLMs.

    I like them 'cause with the right amount, it makes a README easier to parse when quickly scrolling over it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 6 months ago (2 children)

    I like putting the little pictures in my readmes sometimes. In my biologically generated repositories. Please don't discriminate against neat little pictures you can just put in text 🐑.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 15 points 6 months ago* (4 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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 13 points 6 months ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 6 months 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.

  • permalink
  • fedilink
  • source
  • parent