I saw another article today saying how companies are laying off tech workers because AI can do the same job. But no concrete examples… again. I figure they are laying people off so they can pay to chase the AI dream. Just mortgaging tomorrow to pay for today’s stock price increase. Am I wrong?

  • Dr. Wesker@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    1 day ago

    I use it to write my PR descriptions, generate class and method docstrings, notate code I’m trying to grok or translate, etc and so forth. I don’t even use it to actually generate code, and it still saves me likely a couple hours a week.

    • SwizzleStick
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 day ago

      I haven’t thought about using it to annotate my garbage rather than generating its own. Nice idea :)

    • DontTakeMySky@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      1 day ago

      I use it to (semi) automate bit repetitive tasks. Like adding a bulk set of getters, generating string maps to my types, adding handlers for each enum type, etc. Basic stuff, but nice to save keystrokes (it’s all auto complete).

      Anything more complex though and I spend more time debugging than I saved. It’s hallucinated believable API calls way too often and wasted too much of my time.

      • hoshikarakitaridia@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 day ago

        Yeah I can see the API call shenanigans. I’m using super maven for code and it’s pretty good tbh, it gets me 30% of the way or something. But API calls is a no-go, it almost never gets it right because I’m pretty sure it’s very hard for AI to learn the differences in API endpoints.