• SapphironZA@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    4 days ago

    AI development tools are not going away. They are massive productivity enhancers, FOR PEOPLE WHO KNOW HOW TO USE THEM PROPERLY.

    Rather than banning AI tools in development, the correct approach is to change how submissions are handled in open source projects. Maybe we should move away from treating all submissions equally.

    For large projects like the Linux Kernel, you or your organization should go through a qualification process. Alternatives you can look at a referral based qualification. If you submit junk quality code frequently, you lose standing.

    Yes, that’s more work, but it’s worth it for the benefits of AI tooling while retaining the best minds on the project. Arguably large open source projects need this anyway.

      • SapphironZA@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        4 days ago

        Because CEOs are stupid, narcissistic and don’t understand how AI works. Forced use of anything has never resulted in improvements.

        Better to ask the highly skilled professionals who use it effectively and for the correct applications.

        • underisk@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          3 days ago

          There are no correct applications. Even if you accept the dubious claim that its good at coding it would not be good enough to justify the actual non-subsidized costs of using it. Its not just CEOs noting a lack of substantial productivity gains from LLM coding assistants, there are at least a few studies floating around that have examined it.

          Unless you want programming to become nothing but rich MBAs paying Anthropic to turn diesel fuel and your local power grid into vibe coded slop, you should be against AI coding on principle alone.

          • SapphironZA@sh.itjust.works
            link
            fedilink
            arrow-up
            0
            ·
            3 days ago

            Agree, the current market is warping the value argument.

            I am specifically arguing against the use of AI by MBAs. It’s when it is used by the unqualified, when it is at its most problematic.

            The same thing happened in accounting when it first started getting computerised. Suddenly a bookkeeper had the power to affect not just the transactions they were processing, but the entire accounting system. It also happened with managers poking around in systems they did not have proper expertise to use. The solution was not to ban the use of computers in accounting. It was introducing systems and controls around them.

            https://en.wikipedia.org/wiki/Productivity_paradox

            • underisk@lemmy.ml
              link
              fedilink
              arrow-up
              0
              ·
              3 days ago

              I recognize that; what I’m arguing that even when used by qualified professionals (if such a thing could even be said to exist for something so new) the value proposition still doesn’t make sense when you take the real costs into account.

              Progress on AI has bottle-necked and the status quo is unsustainable. They can’t make them cheaper without making them worse, and they can’t make them better without making them exponentially more expensive. If AI continues to exist as a coding tool, it will become prohibitively expensive once capital investment starts realizing there’s no other path to profitability. Then, since programmers don’t control the budgets and don’t get paid well enough to afford unsubsidized AI, it will be made to cater to those that do; becoming a tool for them exclusively.

              The process has already started: Sam Altman trying to take your RAM, NVIDIA and AMD shifting focus from consumer GPU products. If nobody can run local models, then they have no other option but to rent.

              This is why I think If you care at all about the quality of software or programming as a hobby/profession you should be against AI entirely.

    • MoogleMaestro@lemmy.zip
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 days ago

      Rather than banning AI tools in development, the correct approach is to change how submissions are handled in open source projects.

      What kind of recommendation do you have here that doesn’t devolve to, like, closed source?

      Open source requires a community that is transparently involved in the process and have equal rights to fork the code. There’s really no way around this, the license grants the right for anyone to fork as long as they adhere to the license.

      Sad truth is that AI has effectively killed open source unless maintainers are willing to make a clear stance for AI:0 submissions only. Otherwise, the endless pull requests are far too hard to maintain as a single individual. And we certainly don’t want code being accepted by AI systems without human certification, especially in something as fundamental as an OS kernel.

      • SapphironZA@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        4 days ago

        I am not sure that it kills open source. Putting a gate on contributing does not prevent forking and setting up your own project.

        It would also only be required on very big projects. I agree we don’t want bad code accepted, so you need to force people to take responsibility for the code before it gets to a human reviewer.

    • spartanatreyu@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      4 days ago

      AI development tools are not going away. They are massive productivity enhancers, FOR PEOPLE WHO KNOW HOW TO USE THEM PROPERLY.

      It depends.

      To be more specific, they are massive productivity enhancers over the short term with the trade off being lost productivity over the long term. If your scope is going to be over the long term then using LLM tools is going to be a net negative benefit.

      A single small scope disposable project however might be more productive to be vibecoded as the negative effects to the coder (e.g. cognitive debt, skill atrophy, etc…) can be overcome by paying off that debt and reinforcing acquired skills in the next project with thinking through challenging problems and hand coding a larger project.

      But you need to take care to make sure it’s a one off, otherwise you open yourself up to compounding those negative effects. The real danger is the productivity boost from one small scoped disposable project is psychologically seductive and you risk yourself falling into a cognitive surrender / death-spiral. We already know it uses the same pathways as those found in gambling and drug addiction so caution is definitely warranted.

      Rather than banning AI tools in development, the correct approach is to change how submissions are handled in open source projects. Maybe we should move away from treating all submissions equally.

      For large projects like the Linux Kernel, you or your organization should go through a qualification process. Alternatives you can look at a referral based qualification. If you submit junk quality code frequently, you lose standing.

      Yes, that’s more work, but it’s worth it for the benefits of AI tooling while retaining the best minds on the project. Arguably large open source projects need this anyway.

      This can work, but it’s easy to get it wrong.

      Online competitive gaming suffers a similar problem: If all your opponents are bots or cheaters, then the game is no longer fun and players leave.

      The best solution we have for that is shadowbanning. When a user is found to have been cheating, only match them with other cheaters, and don’t tell them. But that doesn’t work in source forges where bad users can tell they can’t communicate with everyone.

      The next best solution is to make it expensive to be a bad actor. Make it so that to participate, you need a paid account (usually a small $5 fee). Bad actor’s accounts are banned and to participate again, you need to jump through the hoops of purchasing a new account. This is used in gaming with purchasing subscriptions (where the credit card number is blacklisted), or by tying a phone number to the account which is sent a validation text message (where the number is blacklisted). This is also used by phone app stores to combat spam app submissions.

      It’s not a perfect solution, but it’s effective.

      • SapphironZA@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        4 days ago

        I agree with the points you raised. We saw similar things happen when computerisation started happening at large scale in business in the 90s. Financial managers raised concerns over lose control and saying their bookkeepers will stop thinking if the computer does the calculations.

        We had to navigate a change in training, processes and structures over the decades to get the full benefit.

        Along the way, we had both people who elevated their productivity and effectiveness and people who could not adapt and became data capturers, adding little value to the process. Much like with vibe coders.

        The technology also has some way to mature. A lot of the problems also stem from the highly subsidized rates people are getting. The tools are accessible to a much greater group of people who are not using them as carefully and deliberately as they should. The quicker this bubble pops the better it will be for all software development.