• Cocodapuf@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      5
      ·
      edit-2
      4 months 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.

      • AwesomeLowlander@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        5
        ·
        4 months 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.

      • Amju Wolf@pawb.social
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 months 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
          arrow-down
          1
          ·
          4 months 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.