Don't listen to your staff? Pay up or shut down for at least a month!
Posted by welvaartsbuik@reddit | talesfromtechsupport | View on Reddit | 36 comments
So I’ve been working at my company for a few years now. It’s a 70-year-old family-run business where people tend to stick around forever — some employees were even hired by the original founder. As you can guess, the general IT knowledge is... let’s say “historic.” Combine that with a “less text = less important” mentality, and you occasionally get monumental screw-ups. Like the one I’m about to share.
We manufacture sensors, and those sensors need to be calibrated. Originally, this was a fully manual process. About 15 years ago, it was “semi-automated” — because why let a computer do something faster and more accurately when a human can take longer and introduce errors?
Fast forward to today, and new ISO standards require full traceability. So we developed a new piece of software: it connects to the CRM, interfaces with lab equipment, controls testing, and logs all changes. Basically, it replaces a Frankenstein system made up of Delphi 5, Excel sheets, and handwritten notes. A big improvement — on paper.
Two weeks ago, our CRM provider announced an upcoming update: database changes, module tweaks, new rules, etc. Alarm bells immediately went off in my head. I warned my manager, the lab manager, and the quality manager.
A week passes. Nothing happens.
Three days before the update, I follow up again. Their response? "The changelog isn’t that big, so we think it’ll be okay. Bigger changelog = bigger changes = more risk. This one’s small, so it’s probably fine." I tried to explain why that logic was flawed, but they didn’t want to hear it.
Then the update hits. Cue total panic.
The lab software breaks. Nothing works. Chaos ensues. "Why didn’t anyone warn us?" "How do we fix this?"
My coworker and I remind them — politely but firmly — that we did warn them. Multiple times. We suggested a dev server. We suggested delaying the update. We even pushed for an SLA with the development agency. But that €15k SLA was “too expensive.”
Now? The company we hired to help with the project is unavailable for a month. So the current “solution” is to have two of our highest-billed employees (both normally booked at over €500/hour) manually patch the database as needed — work that should’ve been automated.
I want to believe they’ve learned their lesson. But deep down, I know they haven’t.
I-WANT-SLOOTS@reddit
What's more risky, open heart surgery or clipping your fingernails? Fingernails, right? You've got 10 fingernails, after all, only 1 heart.
meitemark@reddit
You have backup toenails.
KelemvorSparkyfox@reddit
I've said it before, and I'll say it again.
There's never enough money to do it right.
There's always enough money to do it again.
NotYourNanny@reddit
There are exceptions. Very, very rare, but they do exist.
I was told to make our WiFi "bulletproof." $300,000 later, it is.
It's nice working for people who learn from their mistakes.
testednation@reddit
Ok I'd like to hear how its bulletproof for that price
meitemark@reddit
50KW transmitter. Anything with WiFi or antennas in the nearest area burns up. Then cables to all computers.
Shinhan@reddit
cat6 cables to every computer.
NotYourNanny@reddit
Our needs are modest, and we contracted with people who know what they're doing.
KelemvorSparkyfox@reddit
This is The Way.
Nevermind04@reddit
22mm titanium plating
Hebrewhammer8d8@reddit
Can they always do it again to keep paying me them?
tslnox@reddit
Not always. Sometimes it just breaks down and bankrupts.
capn_kwick@reddit
First mistake: selection of Arthur Anderson as a key player. In the 80s and 90s, the state government agency where I worked used several Arthur Anderson consultants to assist making software updates and new features for our core customer support databases and processes.
Let us just say that the quality of software delivered by AA was well below stellar. Several areas which AA has written had to be rewritten by agency staff because the delivered code so bad.
jb32647@reddit
I work at a company that had some contract work done by Accenture, Arthur Anderson’s successor. It’s god awful and has caused multiple privacy breaches due to user profiles getting data mixed up.
How did this happen? Their contractors would save user data with only the first name and last name as the database lookup fields, instead of something more sensible like, I dunno, THE FUCKING PRIMARY KEY?!?!
WawaTheFirst@reddit
Know the feeling. In our code we've put comments like "start code written by xxx" and "end code written by xxx". When we have to change something in such blocks, we multiply our estimate times 3.
DeciduousEmu@reddit
Hubris and not listening to their key personnel was a big part of the reason that Fox Meyer drug went bankrupt in the early 90s.
grauenwolf@reddit
Context https://cdn.website-editor.net/25dd89c80efb48d88c2c233155dfc479/files/uploaded/Foxmeyer%2520Case%2520study.pdf
And wow. They didn't even bother load testing a database that needed to process 500,000 orders per day. So they ended up with a database that could barely handle 10,000 orders per day.
HobartTasmania@reddit
Given there's 86,400 seconds in every day this sounds really bad.
grauenwolf@reddit
Yea, that math does make it sound even worse.
centstwo@reddit
Said that Fox Meyer went bankrupt and later sued Anderson. Any info on the results of the suit?
grauenwolf@reddit
No, but I was on a phone so I didn't look too hard.
DeciduousEmu@reddit
The list of failures was long and shocking.
DoneWithIt_66@reddit
It's IT, why should we give them money? All that ever happens is they let things get screwed up.
Problem avoided? That's your JOB. Keep doing it.
Impending problem? Deal with it, you seem to know all about what's going to happen so do your stuff.
Spend money? Things are working fine, nothing has blown up in a couple months. We don't need to spend that!
Spend money for a problem that may not exist? You're making a mountain out of nothing, the last update you said that we needed to spend money, nothing happened and those 60 hours of overtime you put in are your JOB. Do it again.
Learn from a mistake? Are you saying it's my fault? YOU'RE the one responsible for the computers.
What do you mean, you warned us? Obviously you didn't do a good enough job explaining what was going to happen or we wouldn't be here.
No, until it happens to them, they will never learn. And even then, they won't be able to see
mwpdx86@reddit
"I want to believe they’ve learned their lesson. But deep down, I know they haven’t."
What they should have learned: oh man, we should have listened to the computer guys, that would've saved us 10's of thousands of dollars.
What they did learn (probably) : those nasty wasty computer guys let the computer stuff get all bad and stinky! Never trust those stinky computer guys ever again!
feor1300@reddit
IT is the most useless department: If it works you're clearly not doing anything. And if it doesn't work you clearly didn't do something!
robsterva@reddit
There exists a perfect response for this: "Big things come in small packages."
Gadgetman_1@reddit
EXPENSIVE things come in small packages.
bstrauss3@reddit
Tiffany & Co.
alf666@reddit
That might be a valid way to beat the owners over the head with the importance of this disaster.
"You think a private jet and your 10th yacht are expensive. You know what else is expensive? The deeds to your mansion and this business, and both of those can be destroyed or corrupted a lot more easily if the right circumstances happen. We are the guys in charge of your business's equivalent to your property and business deeds, so please listen to us when we say that something important needs to be done regarding them."
chalkwalk@reddit
Just make sure you document everything. Everyone hates spending on IT. Sometimes they think they can save on it by removing specialists. You need a paper trail for everything you do now.
welvaartsbuik@reddit (OP)
Everything is well documented. My little team of it/software devs implemented notion and Ms DevOps for these things!
Gadgetman_1@reddit
That's NOT GOOD ENOUGH!
Those are SW tools. That means servers and user accounts. That means inaccessible when your accounts are disabled 'pending investigations' or whatever they use as an excuse.
alf666@reddit
I love how "pen and paper" continues to be the best IT resource in the world.
You can even throw in a copy machine if you want to be fancy with offsite duplicates in a box at a secure location.
Alfred-Register7379@reddit
They haven't, and they'll be bitching about this for years.
beerbellybegone@reddit
This needs to become a case study within the company, really hammer it over their head why it's important to listen to IT
Because if you don't, it's going to happen again and again
welvaartsbuik@reddit (OP)
I hope it lands, I expect it won't. The company had some crazy margins in a very odd market.