hermeticvm on Nostr: On a more positive note though: Leave out the loss of revenue and impact on customers ...

On a more positive note though: Leave out the loss of revenue and impact on customers and there's nothing like a 24+ hour production incident to serve as glue for bonding with colleagues who all keep on showing up despite the many hours we've already spent looking at almost all areas of the client's infrastructure to get services back up.

I wish company leadership would take this to understand that cutting IT budgets and prolonging critical decisions for almost a year just isn't the wisest choice to make if you like your money printer to keep doing its thing.

Probably will never happen though.

Ivory tower dwellers surrounded by yes-men.

quoting nevent1q…m7le

Just witnessed a multinational SaaS provider basically telling their customer to go fuck themselves until morning because they couldn't figure out what broke their system during a production incident. Rude, unprofessional and incompetent.

Their on-call had never worked on this type of system, their network engineers didn't understand their own setup, 2nd level support randomly invented theories that supposedly explained how the customer broke their SaaS, they misconstrued everything we told them to help with debugging to then lie in their final statement for the day.

I'm speechless.

I'll not give names or details for obvious reasons.