• Cocodapuf@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    11 hours ago

    Well, I think it’s legit to use software without understanding the code or use hardware without understanding the specifics of the logical mechanisms of the silicon. But when you’re writing software, you really should know what’s in your own code. Anything else is bad form in my opinion.

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