**SNORT!** Been there, done that earlier in my career. I actually once heard "we won't have a disaster if you simply don't let the systems go down!"
Told me everything I needed to know about the company I was working for. Found a different role OUTSIDE of that company as fast as I could. Their plans were to simply work me to death and then blame me if something went wrong.
Nope. Not. Gonna. Do. It.
Their failure happened in 1974 or so. Some IBM guy threw together something to get them going.
They never corrected it, just kept building on it.
Then the poor guy who had worked on it for 40 years, using the most non-standard practices I have ever seen, got quite ill with cancer (I’m sympathetic having lost a family member). He was so ill he screwed up the code that only he knew.
Guess what? Nobody could fix this thing, not even the gal who had been there over 20 years.
But they expected me to fix it in 2.5 months. I kept telling them I can’t just hack away, it’s going to screw up all the financials. The gal and I tried a few small things but it wasn’t fixing the problem.
So I had to walk away. They weren’t going to let me stay.
Yeah, fix a 40 year old problem in 2.5 months with little or no documentation, not even practical comments in the code.
And believe me, the situation was worse from there.
Sure. I’ll just win Powerball twice a week. That will be easier.
Never saw anything like it. A complete hack job and a total silo. Without any real backups nor development structure.
I was the 2nd person in a row to give up and walk away.
Still, they can’t figure out what their main problem was.