• sparky@lemmy.federate.cc@lemmy.federate.cc
    link
    fedilink
    English
    arrow-up
    17
    ·
    2 days ago

    You’re right, and the corollary is kind of terrifying: instead of N people using one tested, maintained dependency, there will be N similar but non identical LLM generated dependencies, each used by ones of people. Talk about code rot.

    • jj4211@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      19 hours ago

      It’s bad enough in commercial software land where I regularly hit issues because multiple vendors did the same thing in incompatible ways.

      Now slop encourages people to never try to get on the same page.

    • bearforcepilot@lemmy.zip
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 days ago

      This is something I’ve noticed, so many almost the same packages and projects, with very little actual testing

    • Kornclown@feddit.org
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      1 day ago

      I think this is a real dilemma: do you contribute to an existing project, going through the motions of creating pull requests and having discussions or do you just make it yourself. I think there’s still value in collaboration and at leat at the moment it’s not like AI can produce a perfectly polished product without some feedback and direction. But I do wonder, if we are heading towards a world where there’s just an AI operating system which can make you whatever you want. Why share something if it is tailor made for you?

      • aksdb@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 day ago

        I think this is a real dilemma: do you contribute to an existing project, going through the motions of creating pull requests and having discussions or do you just make it yourself.

        This might be surprisingly where a coding agent could motivate me. I typically don’t contribute, because in most of the cases I had the urge to get a missing feature into some piece of software, I had to sink countless hours into understanding their code, getting used to their style, bitching about the choices they made, and/or even setting up a dev environment to test the stuff in (which is often extremely badly (i.e. not at all) documented). This then quickly leads to not-invented-here-syndrome. With a coding agent however, almost all of this becomes irrelevant. The agent can figure out how to run it locally. It can figure out within seconds where in the code I need to make adjustments. If I don’t find an explanation for something in the code, I don’t have to search for ages, I can let the agent do the semantic search in a fraction of the time. Now I can focus on what I actually wanted to do: develop the feature, not doing code archeology for hours.

        • jj4211@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          19 hours ago

          Just so long as your ultimate pull request is plausibly human viable.

          Have been fighting someone because they submitted a 15,000 line pull request for ‘one’ feature and no one is going to review that mess. I gave a very quick ‘for example’ showing in the first 30 lines of changes that it’s screwing around with stuff that has nothing to do with what the sloperator said they pointed out.

          Now they are complaining that I won’t take code even though Claude audited it and said it is all good…

          (This is work, so I don’t have the luxury of just permanently ignoring them).

          • aksdb@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            18 hours ago

            How senior are you? How much senior backing do you have? Close the PR with the comment “unreviewable”. Either they provider smaller chunks, or they can fuck off. If they are unable to prompt properly, that’s on them. They can use Claude all they want, but they should learn how to.

            • jj4211@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              3 hours ago

              Yeah, the things is the processes at work are all driven by optimism, “won’t fix” is not an available option for a bug, and “not bothering” isn’t a valid answer to a PR. And both the owner and reporter must agree on any closure.

              So we end up with perma-issues that can’t be closed.

              I can effectively block the PR, but so long as the submitter wants it open… Doesn’t matter how senior I am.