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 is a most excellent place for technology news and articles.
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 π§
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.
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.
unions would probably make sure all juniors have to work weekends. kinda like airline unions make juniors work 10x unpaid labor hours than the seniors
you are probably thinking of a terrible union. ive been in those, don't bother with them.
how would you know ahead of time? mostly (in USA at least) you donβt get a choice. when you join a job if they have a union you have to join, even if its corrupt. how can you prevent them from becoming corrupt?
in my country you don't have to join it. i generally take a look at what they do and its real apparent when they suck up to bosses.
most unions are like this nowadays over here, but there are good ones.
ah, thanks for explaining that. if there is an option to join or not join, then the unions would have some incentive to do a good job. but in the usa, that isn't an option, so every union eventually turns corrupt.
I'm sure that was done intentionally, to render unions (worse than) useless.
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.
And ~100% of cybersecurity pros work ad hoc 100% of the time...
They probably put in 2-10 hours of actual work in a given week. Just like any desk job that doesn't sit on zoom calls all day.
Edit: 100% of people downvoting this should first Google "ad hoc." Or are just envious that I have a cybersec job making good money doing nothing all day. Sucks to suck. π€·ββοΈ
Kinda how ~100% of IT salaried positions work. If you're confused, you're probably hourly.
If you're paying someone to always be on call then they are always working. Just because you don't always need them doesn't mean they aren't working. You're paying for their availability.
I agree with this but I think point is that yes they are on call all the time but in exchange they get a lot of down time to live their lives.
Not sure it is fair I don't work like that and I don't think I can.
Nurse model seems to make more sense where there is on call list and you get paid for that time.
IMO sitting at my desk, watching logs or waiting for something to come in isn't living my life. I can't do my hobbies, I can't play video games, drink a beer, watch a movie, hang out with my friends, etc. Browsing lemmy or youtube isn't exactly living my life. As long as I'm at that desk, I'm working.
All fair points and agree... If I am on the clock, I am working. Work flow is management issue
If your cybersecurity and/or SecOps team isnβt working 40 hrs a week, youβre either WAY over staffed or youβre missing out on a lot of proactive security work. Ours has a massive backlog of tickets and is working proactively on protecting and preventing incursions and security incidents.
Lol he's got 5 people for 700 users. Way overstaffed. Or well-staffed at a minimum.
700 users is a business group in my world.
Since we're telling people to Google things, try "anecdotal fallacy" and let us know if it helps you to understand the source of the downvotes.
The OP is about survey data that directly contradicts your position. It's fantastic that you've found a position where you have work/life balance that works so well for you, but it simply doesn't match the experience of many commenting in this thread or those who were surveyed.
Be as obstinate as you like, it won't change the lived experiences of others in the industry.
Oh boohoo, you make 6 figures and have to work some weekends. Get over yourselves or better yet, get a job outside of a cubicle. Every job is going to have it's good aspects and shitty aspects.
So would you rather work weekends, or up on a roof in the Florida sun?
False dichotomy, so neither. Things are more work-life balancey in Europe.
You gotta understand the skill set is highly specialized and is ever-evolving. The issue likely being that many take on their six figure salary and aren't paid for their weekend work but instead work to ensure the security of the employer.
If I'm hired for $120k/yr for a 40hr week, but I'm pulling 46-52hr weeks, I would feel the need to be appropriately compensated for it. If it's going to be considered a work hazard I would expect to receive hazard pay.