• Cocodapuf@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      5
      ·
      edit-2
      1 day ago

      I don’t like to use libraries I don’t understand. Probably part why I’m not a professional developer, but it’s the principle of the thing - don’t put out code you can’t vouch for.

      I mean, yes, it’s way easier to just use the library, trust it works; but by that logic, it’s also way easier to just let an llm code for you.

      • Amju Wolf@pawb.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        19 hours ago

        …but do yoz “understand libraries” by reading every line of their code, or by reading the documentation? And only in the parts you’re actually interested in?

        • Cocodapuf@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          17 hours ago

          Yeah, a general understanding is enough. But I think yeah, actually skim over the code, at least get a basic idea about how the internal methods work. Depending on what you’re using the library for, it could be prudent to know more about how data structures are handled.

          Honestly, you’ll probably learn something in the process.

      • AwesomeLowlander@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 day ago

        Probably part why I’m not a professional developer, but it’s the principle of the thing

        There’s no ‘principle’ here, that’s something that simply would not be possible in any sort of large project. To suggest all professional software developers read every line of every library before using it is ridiculously unworkable.

      • mabeledo@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        3
        ·
        edit-2
        3 hours ago

        Libraries can be audited. LLM generated code cannot.

        Edit: to clarify, it is impossible to audit all LLM generated code across a number of projects, that would replace a single library. It simply won’t happen, because there will always be a non trivial number of users who will copy and paste code without inspecting it. In contrast, widely used open source libraries may be audited by a small subset of their users, and the rest would benefit from that.

          • mabeledo@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            20 hours ago

            I know it’s code. You are missing the point.

            Any library with a critical user mass is auditable, because a fraction of those users would take the time to do so, whereas all LLM generated variations of the same library cannot and will never be auditable.

            • Jakeroxs@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              2
              arrow-down
              1
              ·
              19 hours ago

              That’s literally not what you said, you said “LLM code can not be auditable” which is demonstrably wrong.

              Go ahead and move the goal posts though.

              • mabeledo@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                arrow-down
                1
                ·
                edit-2
                13 hours ago

                You missed the context. I don’t blame you.

                Tell me how in hell are you going to audit every single variation of code generated by a LLM, that’s equivalent to a whole library. I’ll wait.