• 9488fcea02a9@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    I’m not a developer, but I use AI tools at work (mostly LLMs).

    You need to treat AI like a junior intern… You give it a task, but you still need to check the output and use critical thinking. You cant just take some work from an intern, blindly incorporate it into your presentation, and then blame the intern if the work is shoddy…

    AI should be a time saver for certain tasks. It cannot (currently) replace a good worker.

    • Lmaydev@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      6 months ago

      As a developer I use it mainly for learning.

      What used to be a Google followed by skimming a few articles or docs pages is now a question.

      It pulls the specific info I need, sources it and allows follow up questions.

      I’ve noticed the new juniors can get up to speed on new tech very quickly nowadays.

      As for code I don’t trust it beyond snippets I can use as a base.

    • Rickety Thudds@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 months ago

      It’s clutch for boring emails with several tedious document summaries. Sometimes I get a day’s work done in 4 hours.

      Automation can be great, when it comes from the bottom-up.

      • isles@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 months ago

        Honestly, that’s been my favorite - bringing in automation tech to help me in low-tech industries (almost all corporate-type office jobs). When I started my current role, I was working consistently 50 hours a week. I slowly automated almost all the processes and now usually work about 2-3 hours a day with the same outputs. The trick is to not increase outputs or that becomes the new baseline expectation.