this post was submitted on 21 Jul 2024
191 points (76.5% liked)
Technology
59211 readers
2636 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've worked in various and sundry IT jobs for over 35 years. In every job, they paid a lot of lip service and performed a lot box-checking towards cybersecurity, disaster recovery, and business continuity.
But, as important as those things are, they are not profitable in the minds of a board of directors. Nor are they sexy to a sales and marketing team. They get taken for granted as "just getting done behind the scenes".
Meanwhile, everyone's real time, budget, energy, and attention is almost always focused on the next big release, or bug fixes in app code, and/or routine desktop support issues.
It's a huge problem. Unfortunately it's how the moden management "style" and late stage capitalism operates. Make a fuss over these things, and you're flagged as a problem, a human obstacle to be run over.
Yep - it's a CIO/CTO/HR issue.
Those of us designing and managing systems yell till we're blue in the face, and CIO just doesn't listen.
HR is why they use crap like CrowdStrike. The funny thing is, by recording all this stuff, they become legally liable for it. So if an employee intimates they're going to do something illegal, and the company misses is, but it's in the database, they can be held liable in a civil case for not doing something to prevent it.
The huge companies I've worked at were smart enough to not backup any comms besides email. All messaging systems data were ephemeral.
That is a damned good point and kind of hilarious. Thanks for the meaningful input (and not just being another Internet Reply Guy like some others on here).
I'm currently working for a place that has had recent entanglements with the govt for serious misconduct that hurt consumers. They have multiple policies with language in it to reduce documentation that could get them in trouble again. But minimal attention paid to the actual issues that got them in trouble.
They are more worried about having documented evidence of bad behavior than they are of it occurring.
I'm certain this is not unique to this company.
FTFY.
Where you spend more time talking about what you're going to do, than ever actually doing it.
Where when you ask for a mirror of production to test in, you're told that Bob was working on that (Bob left 5 years ago).