3 ms·
Looking through the comments, it appears concerns were raised for years and management refused to allow the necessary changes to save money. While you can and
by danjac 6y ago
Looking through the comments, it appears concerns were raised for years and management refused to allow the necessary changes to save money.
While you can and should be the cool head in the room, it's a route to burnout if you end up being the hero who has to keep saving a dysfunctional organization and management from the consequences of its own failures. By all means do your best fix the immediate problem but get the hell out as soon as you can.
- pydry 6y ago>it's a route to burnout if you end up being the hero who has to keep saving a dysfunctional organization The same dysfunction that led to disaster after disaster is likely to lead to very little reward (if any) for actually being the hero, also.
- jart 6y agoReading comments https://www.reddit.com/r/sysadmin/comments/ma4mwl/the_absolute_worst_case_scenario_happened_what/grqlgdw/ https://www.reddit.com/r/sysadmin/comments/ma4mwl/the_absolu... it sounds like he ran into a kernel panic, maybe because cosmic radiation messed with their full disk encryption because they went cheap on the ecc ram, and then he got discouraged, he probably asked management for the resources to rewrite the whole system from scratch, they said no, and then he sat on his hands collecting paychecks for two years until the thing he knew would happen finally happened. How else can you explain an MSP not having a copy of their zone file? That's their core business. It's also no secret in the MSP world how frequently these DNS servers get hacked. I read about it all the time. Especially on Reddit where you can just sense the pervasive fear. So you'd think that'd give a sysadmin a moment's pause to think, OK, have I scp'd my zone file in case that happens to me?