Comment by justin66
2 hours ago
> a library worker doesn't need their computer at 9am so badly that they need an on-call IT worker (and presumably some kind of middle-of-the-night monitoring) to ensure it before they get in.
A single worker probably doesn't, yes. In contrast, hundreds of people being unable to do anything when they come to work in the morning is not a terrible reason to call someone and have them login for a few minutes.
Back to the IA, it seems to me our hundreds of thousands of users, employees and volunteers in time zones across the globe will be unable to access the service until we fix this is a decent reason for an institution that takes its own mission seriously to have an on-call. But you do you.
> Hell, most banks in the US are "closed" for maintenance online for several hours every weekend (or at least they were as of a couple years ago) and no one cares. It's fine.
(this is my industry) Some of their online services are closed, yes. The hours they'll be closed are typically posted ahead of time to minimize the inconvenience to everyone concerned and to display an understanding on the part of the institution that downtime is taken seriously and to signal it is not the result of carelessness. In contrast to online services, most institutions consider it a major failure if something like the ATM system is down for more than a few minutes.
> This attitude is how you waste a ton of money overcomplicating everything while making working conditions terrible for literally no reason.
That's remarkably backwards. The need for humans to be on-call is a result of systems being overcomplicated, not a cause.
If it's only a few minutes, you could just as well fix it at the start of the day. And if it's not, oh well? People can still read books. The librarian can still help them to find a book. If they want to manually track until the computer is back up, they could even still do checkouts.
If those users just say "oh, okay, I'll check back in a couple hours", then okay. Again, this is not hundreds of thousands of people without power or water or something. It's viewing or uploading to an archive. Like, if you're a user, do you really want someone woken up at 3am because you can't use the wayback machine right now? Because "they should take it seriously"? There's a person actually having to deal with that because... you really want to get that one Grateful Dead concert video from their free archive right now? I'm happy to say that yeah I hope their engineers aren't on-call after hours. I would much prefer that they get a good night's rest rather than fix it for me. I hope they're a cool place to work without delusional, psychopathic management.
Perhaps put another way, is there any computer service now that doesn't need a guarantee? Or is everything just critical now?
My point isn't that on-call is overcomplicating, it's that inventing and chasing an SLA often leads to expensive complicated systems (which, ironically, can often directly lead to lower uptime), and on-call has a human cost.
At this point I think you’re just committed to the bit but you cannot possibly believe what you’re writing, as it’s a blinkered analysis and truly misanthropic in its effect. A metropolitan library system employs hundreds of people in a variety of roles and if we can prevent them from having a frustrating and wasteful start to their day, it’s worth an on-call person’s time.
> and on-call has a human cost.
In the context of this thread, we’re talking about this job description:
Senior Datacenter Network Infrastructure Engineer Full Time San Francisco, CA, US 30+ days ago Requisition ID: XXXX Salary Range: $140,000.00 To $200,000.00 Annually
It’s not like we’re talking about indentured servitude or something.
> Perhaps put another way, is there any computer service now that doesn't need a guarantee? Or is everything just critical now?
That’s an interesting strawman you have there. I thought I killed it upthread when I wrote “Depends on the service.”