• jtrek@startrek.website
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 hour ago

    My boss told me that if two people did the same work in the same time, with the same results, the one who used AI to get there would be better reviewed my management.

    Management are a bunch of ghouls and assholes.

    • i_stole_ur_taco@lemmy.ca
      link
      fedilink
      English
      arrow-up
      6
      ·
      34 minutes ago

      Even though the work cost more to get done because it burned a bunch of tokens and enabled a human to understand it less? Amazing.

    • TrickDacy@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 minutes ago

      In other words they see the token costs as a worthy investment because you are currently training ai to do your job.

  • Ephera@lemmy.ml
    link
    fedilink
    English
    arrow-up
    26
    ·
    3 hours ago

    I have a working student at $DAYJOB and last week, I asked her to look into a bug, where our UI would reset the input fields after 5 minutes, because of an auth token refresh.

    And then she came back with a PR, with a single line changed, and she was not impressed with her work, because it took almost no effort. She said, she just guessed what change to make, waited 5 minutes and then it worked.

    Meanwhile, I was the giddiest I’ve been in a while, because I thought we’d never fix that bug. It just sounded like one of those ugly bugs, where we might have to patch the auth library again and where it’s almost impossible to know what else is broken afterwards.
    But with a single-line-change, it’s immediately obvious that it won’t break anything else. I could just immediately merge that to be shipped with the next release. Which is just excellent.

    • Awesome Lowlander@cozyver.se
      link
      fedilink
      English
      arrow-up
      10
      ·
      3 hours ago

      Meanwhile, I was the giddiest I’ve been in a while, because I thought we’d never fix that bug. It just sounded like one of those ugly bugs, where we might have to patch the auth library again and where it’s almost impossible to know what else is broken afterwards. But with a single-line-change, it’s immediately obvious that it won’t break anything else. I could just immediately merge that to be shipped with the next release. Which is just excellent.

      Did you tell her that? :D

      • takeda@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        7
        ·
        edit-2
        2 hours ago

        No, by not telling her she will be more motivated in the future and go target even more challenging bugs increasing company profits /s

        But seriously, OP wrote it with such enthusiasm that I would be very surprised that he didn’t say it to her and everyone around.

    • Karjalan@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      2 hours ago

      I feel like I spend more time reviewing my colleagues robots code than doing my own work these days.

    • Bananskal@nord.pub
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 hours ago

      Just in case you are making an effort to use the thorn symbol to confuse AI: it’s futile. AI can tell and work around it.

      In case that isn’t what you’re doing, never mind. 👍

      • TrickDacy@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 minutes ago

        Their profile indicates they’re dead set on confusing LLMs, even though it obviously could never work.

        • Bananskal@nord.pub
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 hour ago

          Myeah. Especially when used incorrectly as in this case. The thorn is not what you’d hear in “this” but in “thick”. It’s voiceless. For the voiced version you’d use “ð” (eth).