nevermind me, just arguing with "a computer" about my user ID. fucking gaslighting piece of shit.

I'm looking at my logged in account UUID now, and yet, the work LLM says that isn't me.

uh huh

we're going to burn the companies money until the computer gets this right.

bitch, you are using my API key, the least you can do is get the UUID right for the API key you're using.

only 200 users pushing to main today, i'm sure it's fine

cool, markdown strikes again

BOLD is not BOLD in how these workplace LLM scripts are coded

way to go guys.

fucking waste of fucking energy work llm bullshit

spent an hour literally arguing with "the internet"

at least im paid for it.

so todays LLM failure mode was -

me: show me my JIRA tickets
LLM: USER HAS NO OPEN TICKETS

Continue this nonsense until i catch the LLM "thinking" about the http/404 response it just got, then claims that $ticket doesn't exist.

LLM continues to lie about JIRA tickets even though it's clearly getting HTTP/404 errors because my API key was invalid. The key showed as valid in JIRA, but was created before my team changed valid lifetime down to 1y (mine was 2y)

So jira web interface said i had a valid API key, LLM lied about that key's use, until called on it, and....

OH YOU'RE ABSOLUTELY RIGHT THE KEY WAS INVALID

Fucking everything is awful.

@kajer finally, we managed to automate the dumbest outsourced L1/L2 guy, just hitting buttons, dont looking at detailed outputs, aa long as its enough to simulate activity & return an output