• hperrin@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 hours ago

    Tell him this: If you’re writing that much boilerplate (grunt work), you’re probably doing something wrong. If AI can write your normal work, you really should be learning, so not using AI at all.

    • Lovable Sidekick@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 hours ago

      Actually I’m not going to tell a dev with decades of experience that an internet rando thinks he’s doing his job wrong lol.

      • hperrin@lemmy.ca
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 hours ago

        K. It’s astounding to me that after decades in the business, he’s still writing code that can be written by basically an intern.

        When I try to get AI to write my code, it stumbles all over itself just failing to understand the simplest of my libraries. (Literally it made multiple mistakes using the fucking tokenizer library I wrote that is so simple, an intern would have no problem with it.)

        • Lovable Sidekick@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 hours ago

          he’s still writing code that can be written by basically an intern He usually does full-stack projects by himself, so he has to do everything. And he’s using AI to do what interns could do. I’ve dabbled a little using VSCode AI myself to refactor and upgrade a couple hobby projects, and it didn’t “stumble all over itself” at all. In fact it conversed with me like an intern or colleague would, and made many proposals I agreed with. There are ways to craft your prompts that make AI work better. Maybe that’s your problem I dunno.