Depending on what your job is, this is either the adult equivalent of a snow day or some of the greatest stress in a long time.
I have experienced, half a decade ago during some more frequent but less lengthy O365 errors that there are some higher ups who get when this is not something you can fix and some you very much can't. Wishing strength to any "but it's our mail" and "but we bought the Claude" meetings that happen today.
If today is a stressful day it’s probably due to bad management.
I’ve been in this situation before, an external API is basically down and my managers solution is to blame me.
Didn’t last there too long.
People already forgot how to do their work without Claude?
That's a scary thought.
Or if my DeepSeek provider goes down, I switch to the backup and continue working.
> but we bought the Claude
My soul just dry-heaved from laughter. Nice.
I have fond memories of the “we’re a tech company, why can’t we get a video conferencing call going” and gently reminding them that reliable, synchronous, multiparty video conferencing was a lot harder than anything this company was trying to do.
>check my local qmail, dovecot
yeah, couldn't be me
I think it should be fine for most people. Hopefully people don't rely on Claude for Ops, and if it's not Ops-related but just regular coding, I can't see why it shouldn't be able to wait a few days. I mean, even if Claude is down for a month, people should have enough competent developers to keep going, just at a slightly slower pace, right?
There is a third option where it is a minor inconvenience and you learn to adjust and be productive in other ways.