• GreenKnight23@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    that depends on your definition of what a “terrible dev” is.

    of the three devs that I know have used AI, all we’re moderately acceptable devs before they relied on AI. this formed my opinion that AI code and the devs that use it are terrible.

    two of those three I no longer work with because they were let go for quality and productivity issues.

    so you can clearly see why my opinion of AI code is so low.

    • TrickDacy@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      I would argue that it’s obvious if someone doesn’t know how to use a tool to do their job, they aren’t great at their job to begin with.

      Your argument is to blame the tool and excuse the person who is awful with the tool.

      • GreenKnight23@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 months ago

        my argument is that lazy devs use the tool because that’s what it was designed for.

        just calling a hammer a hammer.

        • aesthelete@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 months ago

          Some tools deserve blame. In the case of this, you’re supposed to use it to automate away certain things but that automation isn’t really reliable. If it has to be babysat to the extent that I certainly would argue that it does, then it deserves some blame for being a crappy tool.

          If, for instance, getter and setter generating or refactor tools in IDEs routinely screwed up in the same ways, people would say that the tools were broken and that people shouldn’t use them. I don’t get how this is different just because of “AI”.

        • TrickDacy@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 months ago

          Using a tool to speed up your work is not lazy. Using a tool stupidly is stupid. Anyone who thinks these tools are meant to replace humans using logic is misunderstanding them entirely.

          You remind me of some of my coworkers who would rather do the same mind numbing task for hours every day rather than write a script that handles it. I judge them for thinking working smarter is “lazy” and I think it’s a fair judgement. I see them as the lazy ones. They’d rather not think more deeply about the scripting aspect because it’s hard. They rather zone out and mindlessly click, copy/paste, etc. I’d rather analyze and break down the problem so I can solve it once and then move onto something more interesting to solve.

          • GreenKnight23@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            2 months ago

            sometimes working smarter is actually putting the work in so you don’t have to waste time and stress about if it’s going to work or not.

            I get Dreamweaver vibes from AI generated code. Sure, the website works. looks exactly the way it should. works exactly how it should. that HTML source though… fucking aweful.

            I can agree, AI is an augment to the tools you can use. however, it’s being marketed as a replacement and a large variety of devs are using it as such.

            shitty devs are enabled by shitty tools.