The GNOME.org Extensions hosting for GNOME Shell extensions will no longer accept new contributions with AI-generated code. A new rule has been added to their review guidelines to forbid AI-generated code.

Due to the growing number of GNOME Shell extensions looking to appear on extensions.gnome.org that were generated using AI, it’s now prohibited. The new rule in their guidelines note that AI-generated code will be explicitly rejected

  • Hawk@lemmynsfw.com
    link
    fedilink
    arrow-up
    3
    ·
    10 hours ago

    Its like a gas can over a match. Great for starting a campfire. Excellent for starting a wildfire.

    Learning the basics and developing a workflow with VC is the answer.

      • Hawk@lemmynsfw.com
        link
        fedilink
        arrow-up
        4
        ·
        9 hours ago

        Large language models are incredibly useful for replicating patterns.

        They’re pretty hit and miss with writing code, but once I have a pattern that can’t easily be abstracted, I use it all the time and simply review the commit.

        Or a quick proof of concept to ensure a higher level idea can work. They’re great for that too.

        It is very annoying though when I have people submit me code that is all AI and incredibly incorrect.

        Its just another tool on my belt. Its not going anywhere so the real trick is figuring out when to use it and why and when not to use it.

        To be clear VC was version control. I should have been more clear.

        • theneverfox@pawb.social
          link
          fedilink
          English
          arrow-up
          3
          ·
          9 hours ago

          Okay, that’s pretty fair. You seem to understand the tool properly

          I’d argue that version control is not the correct layer to evaluate output, but it is a tool that can be used in many different ways…I don’t think that’s a great workflow, but I can conceive situations where that’s viable enough

          If I were handing out authorizations to use AI, you’d get it