• 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

          Okay, so if the tool seems counterproductive for you, it’s very assuming to generalize that and assume it’s the same for everyone else too. I definitely do not have that experience.

          • FlorianSimon@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 month ago

            Have you read the article? It’s a shared experience multiple people report, and the article even provides statistics.