• ell1e@leminal.space
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 months ago

    We need the equivalent investment now. If average code is cheap, then the scarce resource is no longer the ability to produce it. The scarce resource is the ability to read it, to navigate it

    You know what would help a lot with understanding the code one is working on? Writing it yourself without turning your brain off via AI.

    But that’s an insight the article somehow seems to be missing.

    • nomad@infosec.pub
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      I always ask myself how many of these anti ai warriors are actually proficient professional coders. And I’m talking like engineer level, not hobby level.

      LLMs are a tool. Give a package power tool to a fool and the result is stupid at best, bloody at the worst. Let’s call that vibe tooling and ask if there is a difference to vibe coding.

      Imho there is not. LLMs are a tool that can lift up the quality of coding work to a common level if used by proficient people. It helps with searching through and understanding vast outputs as long as you know what to expect. Its a miracle in intuition.

      Its not a mind reading tool that will just code your fantasy software for you. Hate it all you like, AI is here to stay, this is like hating cars in the age of horses. Cars are not magic, neither is “AI”.

      • darkmarx@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        6 months ago

        I have over 25 years of development experience. My current role is vice president of development and architecture where I lead a team of 80+ devs, QAs, and architects. By any measure, I am one of those “engineer level” developers you speak of.

        Yes, LLMs are a tool, but it’s a tool one should use sparingly. LLMs are pattern recognition machines and are great for routine, been-there-done-that type development. For anything that deviates from the norm, LLMs will try to force everything back into common patterns… even when those patterns are not correct. A well designed system can be mangled into junk because the LLM doesn’t have enough context or because something is new.

        Be skeptical of the rave reviews around coding agents and the use of LLMs for development. Much of the hype seems tied to developer skill. Less capable developers can use LLMs to appear more capable than they are. For good developers, LLMs seem to erode their skills as they rely on the tool instead of their own knowledge. I have seen this first hand.

        Overall, it seems LLMs raise skills of bad developers and hamper the skills of good developers. It’s creating a bunch of middling developers who are incapable of handling anything novel or complex.

            • onlinepersona@programming.dev
              link
              fedilink
              arrow-up
              0
              ·
              6 months ago

              I’m not pro AI or anti AI. I am anti big tech though, which makes the discussion more complicated.

              Regarding escalation, a non coding team lead isn’t a dev. A CTO isn’t a dev. A software architect isn’t a dev. A software developer is a dev. That’s not an escalation, it’s a fact.

              Just because you lead a team of devs, doesn’t mean you are a software developer, you could’ve gone to business school, never written a line of code and just started leading a team of software developers because you learned “how to lead”. And there are different kinds of team leads, those that get their hands dirty and those that don’t.

              So no, being a CTO, CEO, or whatever C you want to put in front of your title doesn’t make you “far exceed” any qualification. I actually think that kind of thinking is the problem workers are underpaid: people who lead actually often exceedingly overestimate their abilities in the craft they lead. “I lead a team of athletes, that means I’m a good athlete”. Do you understand how crazy that sounds?