• Hackworth@piefed.ca
    link
    fedilink
    English
    arrow-up
    17
    ·
    22 hours ago

    Yup! Certifying a workflow as AI-free would be a monumental task now. First, you’d have to designate exactly what kinds of AI you mean, which is a harder task than I think people realize. Then, you’d have to identify every instance of that kind of AI in every tool you might use. And just looking at Adobe, there’s a lot. Then you, what, forbid your team from using them, sure, but how do you monitor that? Ya can’t uninstall generative fill from Photoshop. Anyway, that’s why anything with a complicated design process marked “AI-Free” is going to be the equivalent of greenwashing, at least for a while. But they should be able to prevent obvious slop from being in the final product just in regular testing.

      • plateee@piefed.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        15 hours ago

        Or just have a hard cut-off for software released after 2022.

        It’s the only way I search for recipes anymore - a date filter from 1/1/1990 - 1/1/2022.

      • Hackworth@piefed.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        22 hours ago

        Coincidentally, this paper published yesterday indicates that LLMs are worse at coding the closer you get to the low level like assembly or binary. Or more precisely, ya stop seeing improvements pretty early on in scaling up the models. If I’m reading it right, which I’m probably not.

    • Bronzebeard@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      19 hours ago

      Yeah, do you use any Microsoft products at all (like 98% of corporate software development does)? Everything from teams to word to visual studio has copilot sitting there. It would just take one employee asking it a question to render a no-AI pledge a lie.