Seems like he’s been pushed into using LLMs as a way to cope with the deluge of LLM-generated security reports.

  • FizzyOrange@programming.dev
    link
    fedilink
    arrow-up
    39
    arrow-down
    5
    ·
    2 days ago

    I think there would be a lot less drama around this if authors were just up-front about how they use AI. Put it in your readme, just like you do with licenses.

    • Lauchmelder@feddit.org
      link
      fedilink
      arrow-up
      20
      arrow-down
      3
      ·
      2 days ago

      The commits were literally in plain sight. If people didn’t notice it from that alone, then a disclaimer in the README would have gone unnoticed either. The project received several github issues contributing nothing but “remove the AI slop” to the project. If this is the reaction you get for using AI openly, then don’t be surprised when more devs just don’t disclose AI use at all

      • FizzyOrange@programming.dev
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        2 days ago

        Why not? I’ve added it to my projects. It’s simple, just open README.md. Write “# Use of AI. This project does not currently use AI. / This project is entirely vibe coded & I don’t read the code at all. / I occasionally use Claude Code but thoroughly review its output.”

        Save. Commit. Push. How is that not straightforward?