When declaring an incident becomes everyone's favorite workaround
greatcircle.comI don't usually comment about LLM-written articles, but it feels like an especially bad idea to do so in an article where you promote a book you're writing. Will that be LLM output, too?
https://www.pangram.com/history/9c8f8da8-0b4d-48d6-be23-9e8a...
I wonder how it determines that part of the text was AI written
Not sure, but I intentionally included the opening paragraph because I spotted the writing style switch when I got to the second paragraph. So then ran it on Pangram to confirm.
edit: to be clear, if you click the details, the "70%" refers to the fact that it thinks the opening paragraph is human written (or edited), and the rest is 100% AI with "high confidence".
Which is why the only people authorised to declare an incident are your incident managers. They follow the published guidelines which dictate what's a Sev 2 and what isn't.
A manager of a service may not declare their own service a Sev 2. If they can, your incident management process is broken.
Maybe there's the option of hiring better people as well so you don't have to babysit them at this level. If you can't trust teams to open incidents maybe the problem lies somewhere else.
Reporting incidents as sev-2 that obviously aren't, across state lines, electronically, to secure employment is wire fraud.
Once your corporation normalizes serial felon behavior, stability goes down the drain.