• tmyakal@infosec.pub
      link
      fedilink
      English
      arrow-up
      68
      arrow-down
      1
      ·
      8 hours ago

      Anecdotally, my job trained every office employee on AI tools back in March, encouraging everyone to think of ways to incorporate the tools into their standard work. As of last week, they’re asking us to get prior authorization to use their AI portal as a way to limit requests.

      So some Fortune 500s must be feeling the squeeze on AI.

      • partofthevoice@lemmy.zip
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        2 hours ago

        Hi, it’s partly my fault. You’re welcome. Boss said use more AI. Boss’s mistake was asking someone who would actually take him seriously, unlike all the koolaid chugs out there. Made a docker runtime harness that hooks up to Snowflake Cortex Code SDK for inference. Supports defining repeatable LLM tasks, scheduling them, lightly orchestrating them, network controls, saving results, … It’s got support for custom skills, commands, chain prompting, sessions, … So now I can use Docker to schedule LLM jobs like motherfucking database pipelines. It can mediocrely do shit like research, planning, evaluations, … all defined through YAML configuration files.

        Basically, I introduced scalability to the stack. Sweet malicious compliance. We’ll see what happens next, when everyone is actually empowered to use AI like the execs want. My prediction is an about-face.

        Edit: sometimes the best way to win a fight is to show the referee that the rules don’t make any fucking sense. Sometimes the referee doesn’t speak English, though, so you have to show them via USD speak. Sometimes they have a hard time hearing too, so you have to let them taste the poison a little. Sometimes they get drunk off that little bit, so you then gotta throw them in the fucking pool and tell them to start swimming.

      • funkless_eck@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        30
        ·
        7 hours ago

        yep. everyone at mine was being praised for creating an agent that turned meetings into JSON and then the JSON into Asana tasks and the Asana tasks into a report and the report into an internal and external email and the email into a slack message and the slack messages and emails into weekly summary.

        Burning thousands of credits for what could be replaced by…

        listening

        • BackgrndNoize@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 hour ago

          All that and you know for a fact no one’s reading any of that crap. I hate that working as an adult involves working with spineless losers who would rather participate in this clown show than call it out, because being real gets you punished

        • BassTurd@lemmy.world
          link
          fedilink
          English
          arrow-up
          16
          ·
          6 hours ago

          I created a PoC to have an event parse an employees emails, summarize them, then check the calendar and recommend meetings and follow up based on context. It ended up working okay, but it was such a waste of time. This was a C Suite employee that requested, who gets a high volume of junk email. Why would you want AI to (initially requested) auto create meetings for you? That sounds like my nightmare. In the end, it never hit prod thankfully, but, the dev work to get to where I did was awful. Developing AI agents is like guessing and checking until you get close enough. Debugging is brutal and the work is extremely uninspiring.

      • BassTurd@lemmy.world
        link
        fedilink
        English
        arrow-up
        16
        ·
        6 hours ago

        I was put in a position to start building and deploying copilot agents in our company. I discovered in the first day how unprepared our environment was for anything copilot. The default state when you get licenses and an environment to work in, is the wild west. It’s really bad and as is tradition, half cocked and rushed to market. I wrote out pages of notes of things we had to do as a company before even the most simple agents are created for security and governance. I never got the support to implement any changes, so I drug my feet as much as I could on anything I could. For 6 months I successfully never deployed any AI stuff and got out to do full stack dev instead. I created PoC agents, but with hard caveats that none of it was usable in the current state in prod.

        Now prices are increasing and our drive to force agentic has softened a little company wide. I like to think that my semi malicious yet justified slow walking saved us a whole shit load of headache and expenses over the next couple of months as the new copilot pricing hits on June 1.

      • Squizzy@lemmy.world
        link
        fedilink
        English
        arrow-up
        30
        ·
        7 hours ago

        Christ I am only realising now they probably see me asking copilot “why are you so shit” or “Just fuckoff, I’ll do it myself”. They pay for that.

        • jballs@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          4
          ·
          4 hours ago

          Unfortunately that reality is going to quickly turn to “we have to cut staff and freeze salaries this year due to AI spending”.

      • BarneyPiccolo@lemmings.world
        link
        fedilink
        English
        arrow-up
        13
        ·
        7 hours ago

        Now that they’ve poured zillions into it, they are starting to realize that they’ll never get their return on that investment, so now they have to manage the draw down so it doesn’t all crash.

        At least some are recognizing it.