yeah fuck that, i don't want 24/7 work just because they can theoretically reach my almost dead carcass 24/7.
we need unions asap π§
this post was submitted on 19 Jun 2024
271 points (97.9% liked)
Technology
59882 readers
5253 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
I mean, as long as its on-call hours paid according only, sign me up.
i got that, the stress is not worth it. the previous generation didnt need to work 24/7 every week to earn what i did with all the commissions included.
get people to rotate out with me. i'd rather get less pay (provided its sufficient for living) than the chronic stress.
I mean yeah, in a rotation. And when I wake up in the night I'm still entitled to 12 hours of rest before I start working the next day.
i wish! 12 hour rest after a shift would have been awesome.
That's the law in many European countries.
i'm in an ~~european~~ american colony, so we don't have that anymore.
Change Windows. You can't take shit down during the work day.
Everywhere I've worked (many very large companies, banks, telecom, outsourced IT, etc) teams have coverage schedules, so I suspect this article is misleading.
Someone has to mind things 24/7, this is done via scheduling.
And the more critical you are, the more on-call you are. I had one role where I was on call 24/7. Things rarely broke enough for me to be called, but I never once resented when I was called. I'd rather get woken up at 2am because my help is needed than have the risk that our systems aren't ready for the day.
And the more critical you are, the more on-call you are.
This shows a really low Bus Factor which should be remedied. If you're on call 24/7 because you're the only person who can fix things then your employer is running the risk of you being unavailable due to injury or disease and then they're up shit creek sans paddle.
There are no bad employees only bad managers, or some karate kid nonsense like that. I had a job where I was "on call" 24/7 with no one else as alternates. I kept getting in trouble for not being available on the weekend when they called me. Most of the other employees I worked with in similar positions admitted to drinking every night that way they couldn't get called in after hours. I quit that job quick.
that is if they actually allow you to make the changes so the systems are reliable.
theres always some boss that doesn't want to swallow his pride and you pay the price for it.
That wouldn't be cybersecurity though, right? That sounds more like a (dev)OPs role.
Not to mention that lots of malicious attacks occur late at night or on weekends in an attempt to delay getting noticed. My company has rotating on-call schedules for our security, devops, and even engineering teams. Iβve had to hop on late at night or on weekends to help mitigate attacks. Luckily my employer is really good about letting folks take a day or two off after such events.
While I nominally agree, there are some situations and contexts in which an on-call rotation is not only appropriate, but the responsible thing to do.
That said, on-call people should get special compensation/rewards/perks, because being on call sucks.
on-call people should get a rotation so they aren't on call every single week. which is what usually happens ime.
At the very least, we need to codify comp time as policy, overtime as law.
High availability and security are the bane of IT infrastructure jobs. It makes me anxious to think about my MSP days when I'd sit on my couch on a Saturday fully aware that I'm one phone call away from having my day, weekend or even the next two weeks ruined because some customer CEO has full domain admin rights and would give them to anyone who'd ask on the phone or via email.
It's not just security that ruins an IT person's life. I had a customer decide to do a massive data migration from their primary data storage to a new system during the busiest time of day. It destroyed the primary, secondary, and backup systems as well as corrupting the destination system. It was a one-in-a-million bug/glitch that cost me 2 weeks of 16 hour days.
It's idiots in charge of IT that are the true source of our pain.
My org has a follow-the-sun rule and avoids having people work on weekends. It helps that it's a global team, so there's only around maybe 18-20 hours in the middle of the weekend where it's not a Monday or Friday somewhere in the world.
My company doesn't work weekends unless you're on call or something. I could see it happen with incident response or security operations, but other things aren't so critical that we need to have our staff working outside of normal business hours.
I may be lucky as well because I work within GRC, and we have a huge focus on work-life balance.
This 70% number seems high. I'm in leadership.
No shit