Hacker News new | past | comments | ask | show | jobs | submit
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.

There is a third option where it is a minor inconvenience and you learn to adjust and be productive in other ways.
No, and that's also not necessary. We are reliant on our systems. The correct response is to harden our systems, not to foster some illusion of independence.

We can of course do that privately, for just the heck of it, but it's not the right response for anything at societal level. We simply need to work harder for more of these 9s

loading story #50481991
You’re not wrong, but some companies swing real hard at the biggest players assuming they won’t all be down at the same time. My work has hard dependencies on 365 and Cloud Entra and only allows Claude company wide. Today is going to be a snow day since we couldn’t get into anything yesterday but we could at least get projects done using connections Claude had into various platforms that cached the data in 365.
loading story #50481992
loading story #50482053
There is always something that you can do that isn’t gated by the api. It isn’t critical path for literally everything. Go organize your expense reports or something.
loading story #50482602
loading story #50482826
loading story #50482692
loading story #50481707
loading story #50481863
loading story #50481936
Finally having time to vacuum clean the office
loading story #50481748
loading story #50481878
loading story #50482448
loading story #50482380
loading story #50481891
loading story #50483010
People already forgot how to do their work without Claude?

That's a scary thought.

loading story #50481971
loading story #50481900
loading story #50482223
loading story #50481920
If you are that reliant on LLMs for your workflow, then how do you not have any redundancy in place? Assuming you've have any kind of basic abstraction in place, swapping in API keys for a different provider should be a simple config change...
loading story #50482600
loading story #50482673
loading story #50482610
loading story #50482809
Or if my DeepSeek provider goes down, I switch to the backup and continue working.
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.

Just as you described. Snowday for some... I was caught in between snowday and stress today with these things. Got too used for claude to just do most things.

But at the same time was surprised I could still google and resolve things myself when I started thinking again lmao.

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?
loading story #50481689
loading story #50482517
loading story #50481528
loading story #50481519
loading story #50481524
loading story #50483059
The most likely scenario, is their team of high achievers, deployed a massive pile of stinking technical debt, against the advice of the experienced folks who are constantly overridden.

On a normal environment the old Graybeards would fix it, after grumping on being taken away from playing with their latest Emacs config.

But this is the Valley, and we dont do experience only VibeOps. And half reading this post, are wondering if Emacs is a new frontend framework they never heard about....

> 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.
loading story #50482833
> O365

O364...

loading story #50481647
loading story #50481800
loading story #50481693
Anybody who has based their workplace on MS and Claude having 100% uptime kind of should take responsibility though
loading story #50482590
>check my local qmail, dovecot

yeah, couldn't be me