We aren't. But it's generally better for patient care. It's the same nurse/doctor seeing through more of the care of a patient with less handovers.
Handovers are where minor details or context can be forgotten, dropped or misunderstood - especially after a really tough shift.
Patients also get to see the same faces more often, which makes them feel like they are being taken care of - as opposed to a part being made in a machine.

But it's wrong. It would be better to have 8 hour shifts with 2-4 hour overlaps between shifts. So it's not a handover, it's an actual rounds, it's actually servicing patients and so on.
But that is likely very intrusive for patients, and 4-8 hours of the shift is with someone else (who you might not like or agree with) and communicating (which can be tiring).

So yeh, it's not great. Understaffing doesn't help, especially since these are people that genuinely care about their work. It's pure exploitation, because it is cheaper and hospital administration can justify it and get away with it (or whatever is higher that hospital admin in the case of free healthcare).

In some cases, it's budget and exploitation. And it's bullshit.
But there is a genuine argument that a doctor who is fully informed and tired is better than a doctor who is fresh and oblivious.

FCKGW?

There is a statue in Glasgow that always has a traffic cone on its head.
The council regularly removes it, and its always replaced.
It's had different variations over the years, from pride to independence to EU flags.
The council proposed a renovation of the statue including raising the plinth to make it harder to replace the cone. It was shot down with massive public outcry.

https://en.wikipedia.org/wiki/Equestrian_statue_of_the_Duke_of_Wellington,_Glasgow

Oh, it's expected costs.
Like, figure out the compute requirements of your code, multiply by the cost per compute unit (or whatever): boom, your cost.
Totally predictable.
Compared to suddenly having to replace a $20k server that dies in your data center.
So much easier.

Except when your code (let's be honest, the most likely thing to have an error in it... At least compared to some 4+ year old production hardware that everyone runs) has a bug in it that requires 20x compute.
But maybe that is a popularity spike (the hug-of-death)! That's why you migrated to the #cloud anyway, right? To handle these spikes! And you've always paid your bills so... Yeh, here's a 20x bill.

Unlike the reference series, the comment was not done in 1 take and didn't have the budget for professional editing.

SystemWaylandD

I love the callback to compiling
(Edit: it's an old one: https://xkcd.com/303/ )

Are you 100% sure it was a form from a bank?
Everything stinks of a scammers phishing form, leading to scammer calls.

I expect the only time a bank is going to want your phone number is when you initially sign up with them. After that, they should know who you are and your contact details.

I almost got caught out by a "sorry we missed you" delivery message, until it was asking for my date of birth.
Some of these random emails and SMS can catch you off-guard and seem legit

The xkcd explained brushes near it.

Many of the passengers would suffer extreme injuries from the changes of velocity (up to 230 mph based on a loop radius of 3 x ship length) and rotation (unlike rollercoasters, or even airplanes during simple take-off and landing, passengers aren't normally strapped down).

Those "once in a lifetime" or "once in a decade" weather events seem to be quite common these days

Without recognising the picture, and having never played rimworld...
I'm going to guess the picture is from the game Rimworld.

And I'm basing this on the context that this community is called "rimworld"

I guess the obvious one is "holding spacebar for control key"