• tomalley8342@lemmy.world
    link
    fedilink
    English
    arrow-up
    86
    arrow-down
    1
    ·
    11 hours ago

    Job Requirements:

    Active use of AI tools in daily development workflows, and enthusiasm for helping the team increase adoption

    Nice to have:

    Passion for games and game preservation

    AI Mandatory, game preservation optional. Glad they got their priorities straight 😅

    • criss_cross@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      6 hours ago

      It’s kind of the new loyalty test you have to pass for companies nowadays to get a dev job.

      “Oh yeah I love AI and want to be replaced by robots. Spank me harder daddy”.

    • Calfpupa [she/her]@lemmy.ml
      link
      fedilink
      English
      arrow-up
      30
      ·
      11 hours ago

      enthusiasm for helping the team increase adoption

      Seems like they want to hire an AI salesman, not an engineer.

    • HarkMahlberg@kbin.earth
      link
      fedilink
      arrow-up
      7
      arrow-down
      1
      ·
      10 hours ago

      Here’s the secret: talk a big game about being pro AI in the interview, then just don’t use it on the job. What are they gonna do, grab your hands and put your mouse cursor on the Copilot button?

      • tomalley8342@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        7 hours ago

        Copilot business subscriptions have fairly granular usage tracking, so they’d probably just replace you right away with someone who isn’t quite so reserved. Looking at the comments here and in other places, there is certainly no shortage of such people.

    • tempest@lemmy.ca
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      6
      ·
      10 hours ago

      Honestly if part of their job is at all trying to get old shit to run on new operating systems AI is very useful for that task.

      Part of my job is keeping a 30 year old c++ application compiling and building on newer versions of Linux. LLMs have made this a far easier experience.

      • Cethin@lemmy.zip
        link
        fedilink
        English
        arrow-up
        7
        ·
        7 hours ago

        I don’t want to say you’re totally wrong, but I am skeptical of the benefit. Sure, maybe it works now, which is cool, but is it making changes that are maintainable? The next time someone does this is it going to work? If we just constantly have LLMs update code, when does it start breaking, and when it does is it going to be in a state someone can fix?

        • tempest@lemmy.ca
          link
          fedilink
          English
          arrow-up
          4
          ·
          6 hours ago

          Im not generally making source code changes. It’s the dependencies.

          Mainly we’re talking about building very old versions of things like libpng. Making things like autoconf and configure and cmake all work is a pain in the ass as their versions slowly change.

          The business would be content to let it run on Ubuntu 12 until it’s a major problem so I can’t let the perfect be the enemy of good.

          • Cethin@lemmy.zip
            link
            fedilink
            English
            arrow-up
            1
            ·
            3 hours ago

            Fair enough. Probably a good use case for it. I’ve found it’s pretty reliable at creating boilerplate. I just wouldn’t trust it for doing anything important.