For me:
Sometimes it doesn’t matter how hard you work, your going to get laid off either way.
Just showing up can sometimes make the difference.
Your not paid to be a software developer. Your being paid to be a problem solver.
For me:
Sometimes it doesn’t matter how hard you work, your going to get laid off either way.
Just showing up can sometimes make the difference.
Your not paid to be a software developer. Your being paid to be a problem solver.
Validate your backups regularly.
Also, make backups.
Taking a day to actually test backups by doing a cold reset can save a business, thats for sure.
The horror of being a senior admin is realizing that the whole thing could live or die based solely on your actions and decisions. And that you will be blamed.
This is where you bring Chaos Monkey in and see where your weak points are.
I’ve always wanted to deploy Chaos Monkey for its actual purpose, but I’ve never been in charge of a big enough infra to make it worth the time. I have turned off databases just to see who files a ticket, which seems in the same spirit.
A shout test is what I call that.
If your backups are untested, you don’t have backups.
Years after the fact I could make the lead developer’s eye twitch just by mentioning the guy who was supposed to maintain the backups but we discovered after the fire that he actually hadn’t been doing it. That guy was fired, but it didn’t bring back the lost code.
Wait, you didn’t have some git-based thing with an off-site upstream?