[–] 5 points 1 year ago* (2 children)

Opens ticket

Ticket only says “read customer email and advise”

Email chain is a mile long going back 3 months

Closes ticket with “please clearly and concisely explain the problem in the next ticket you open”

3 day SLA on our tickets, so back to the end of the line they go.

  • source
  • [–] 17 points 1 year ago* (last edited 1 year ago)

    Little over a decade ago I dealt with internet on trains. One ticket read "internet doesn't work".
    No info who submitted it.
    No info when.
    No info which carriage.
    No info which train.
    No info which route or any other clues as to the geographical location. Could have been inside of a tunnel for all I know.

  • source
  • [–] 25 points 1 year ago (1 child)

    This is actually where a phone call can be beneficial if you’re assertive about the questions and cut them off when they get squirrely. Some people will never figure out how to get to the point over a ticket because they cannot organize their thoughts no matter how well formed your written instructions are. Get them on the phone and just remote to their workstation.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago

    There would be no way to do that reliably. There's too much weird stuff people might say to reference things, and the LLM would definitely act on the wrong cells more often than not.

    Excel already has a perfectly unambiguous way to provide a specific range of cells, Which is why the =COPILOT() function lets you supply those in the second parameter. I'm assuming they get passed to the LLM as context, likely encoded as a markdown table. LLMs love parsing markdown, apparently.

    The user provided no such range of cells, though, so the LLM is most likely seeing none of those other cells, and is just working based on random values from the Internet.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago

    For all of its faults, the Windows Server ecosystem is incredibly good at providing graphical configs for everything that you'll need for a small to medium sized business, and Windows servers can really survive a surprising amount of abuse. For most things it's at least acceptable, and on a couple of things (Active Directory with Group Policy, as well as RDP) it's best in class and very difficult to beat

    Of course all of Microsoft's killer products were built at least 25 years ago by engineers who've long since left the organization and it shows. Microsoft is trying so hard to move everything to Azure so they can charge monthly for access, yet everything they build into Azure is somehow worse than the on-prem alternative and as they stop updating on-prem options and keep forcing more and more migration into Azure businesses are going to get more and more frustrated with the constantly rising costs and constant loss of quality. Oh and whenever there's another Azure outage it's going to be increasingly un-fun as everything migrates into Azure

  • source
  • parent
  • context
  • [–] 2 points 1 year ago (1 child)

    Hilariously that's part of how Facebooks llama.cpp local chatbot became so popular. It was initially released only to researchers and research institutions but someone rapidly uploaded it to some warez sites and the cat was out of the bag from there. Subsequent releases of llama were released under far more permissive licenses after it became clear that it wasn't as dangerous as they feared

  • source
  • parent
  • context
  • view more: ‹ prev next ›