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

  • i_stole_ur_taco@lemmy.ca
    link
    fedilink
    arrow-up
    85
    ·
    7 天前

    extension developers should be able to justify and explain the code they submit, within reason

    I think this is the meat of how the policy will work. People can use AI or not. Nobody is going to know. But if someone slops in a giant submission and can’t explain why any of the code exists, it needs to go in the garbage.

    Too many people think because something finally “works”, it’s good. Once your AI has written code that seems to work, that’s supposed to be when the human starts their work. You’re not done. You’re not almost done. You have a working prototype that you now need to turn into something of value.

    • skepller@lemmy.world
      link
      fedilink
      arrow-up
      11
      ·
      6 天前

      Too many people think because something finally “works”, it’s good. Once your AI has written code that seems to work, that’s supposed to be when the human starts their work.

      Holy shit, preach!

      Once you give a shit ton of prompts and the feature finally starts working, the code is most likely complete ass, probably filled with a ton of useless leftovers from previous iterations, redundant and unoptimized code. That’s when you start reading/understanding the code and polishing it, not when you ship it lol

    • Jankatarch@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      edit-2
      6 天前

      Just the fact that people are actually trying to regulate it instead of “too nuanced, I will fix it tomorrow” makes me haply.

      But they are also doing it pretty reasonably too. I like this.

  • itsathursday@lemmy.world
    link
    fedilink
    arrow-up
    78
    ·
    7 天前

    You used to be able to tell an image was photoshopped because of the pixels. Now with code you can tell it was written with AI because of the comments.

      • NOPper@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        17
        ·
        7 天前

        I’ve been in the habit of putting the filename as first comment in most of my scripts forever. I don’t know when or why I started but please don’t make me change!

        • ozymandias@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          9
          ·
          7 天前

          it’s how example code is often written when it’s i. a book or a webpage… there’s not really a good reason to do it in a real file because it’s in the filename.
          but if it helps you organize it doesn’t hurt anything.

        • Ænima@lemmy.zip
          link
          fedilink
          arrow-up
          1
          ·
          6 天前

          I add a comment to he first line of unsaved files because that’s what Code displays for the tab name and it either helps or confuses me about what is in the tab.

    • NotSteve_@piefed.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      6 天前

      # Optional but […]

      edit to explain my very vague comment: ChatGPT loves to offer code with some lines commented as “Optional [… explanation]”. You can easily tell AI code when the monologuing comments are left in

  • buddascrayon@lemmy.world
    link
    fedilink
    arrow-up
    14
    ·
    5 天前

    This is one of the things that people who use AI to vibe code don’t get. Sure your AI genned code ends up working but when you actually look at the code it’s sloppy as all fuck, with a lot of unnecessary junk in it. And if you ever have to fix it, good fucking luck finding what’s actually going on. Since you didn’t write it there’s no way for you to know exactly what it is that’s actually fucking up.

    Really you end up being no better than some homebody who copy-pasted some code they found on the internet and plugged it into their shit with no idea of how any of it actually works.

    • IngeniousRocks (They/She) @lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      27
      ·
      edit-2
      6 天前

      Just an example:

      I’m a programming student. In one of my classes we had a simple assignment. Write a simple script to calculate factorials. The purpose of this assignment was to teach recursion. Should be doable in 4-5 lines max, probably less. My coed decided to vibe code his assignment and ended up with a 55 line script. It worked, but it was literally %1100 of the length it needed to be with lots of dead functions and ‘None->None(None)’ style explicit typing where it just simply wasn’t needed.

      The code was hilariously obviously AI code.

      Edit: I had like 3/4 typos here

    • brian@programming.dev
      link
      fedilink
      arrow-up
      18
      ·
      6 天前

      if it’s not clear if it’s ai, it’s not the code this policy was targeting. this is so they don’t have to waste time justifying removing the true ai slop.

      if the code looks bad enough to be indistinguishable from ai slop, I don’t think it matters that it was handwritten or not.

    • kadu@scribe.disroot.org
      link
      fedilink
      arrow-up
      15
      ·
      6 天前

      I guess the practical idea is that if your AI generated code is so good and you’ve reviewed it so well that it fools the reviewer, the rule did it’s job and then it doesn’t matter.

      But most of the time the AI code jumps out immediately to any experienced reviewer, and usually for bad reasons.

      • refalo@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        6 天前

        So then it’s not really a blanket “no-AI” rule if it can’t be enforceable if it’s good enough? I suppose the rule should have been “no obviously bad AI” or some other equally subjective thing?

      • AllHailTheSheep@sh.itjust.works
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        5 天前

        wow. that dude is a piece of work. made the mistake of clicking one of the links to his blog, and wow. there’s a stunning lack of knowledge or self respect there

  • Stern@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    7 天前

    Good.

    I’m mostly switched off SAMMI because their current head dev is all in on AI bullshit. Got maybe one thing left to move to streamerbot and I’m clear there. My two regular viewers wont notice at all but I’ll feel better about it.

  • danhab99@programming.dev
    link
    fedilink
    arrow-up
    6
    ·
    7 天前

    So what does this mean? Bc like (at least with my boss) whenever I submit ai generated code at work I still have to have a deep and comprehensive understanding of the changes that I made, and I have to be right (meaning I have to be right about what I say bc I cannot say the AI solved the problem). What’s the difference between that and me writing the code myself (+googling and stack overflow)?

    • fodor@lemmy.zip
      link
      fedilink
      arrow-up
      4
      ·
      7 天前

      What’s the difference? Jesus, we have seen the difference in the news for the past year. You know the difference. Don’t play dumb now.

      • De Lancre@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        6 天前

        We still talking about extensions, right? Those things in gnome, that shows weather or time in different time zone?

        Cause if yes, your response is kinda weird. Oh no, my weather applet is created using AI! Everything will fall apart! Jesus Christ, we need to burn author for that!