Blaming everyone but yourself as a systems engineer
As a systems engineer, I’ve always been very close to complains and blames. It’s not rare seeing things break. Code bugs, platform bugs, unexpected behaviors in the platform, etc.. Several things may lead to an outage or any other type of service degradation. And in these cases blames and complains start appearing everywhere.
Today AWS (Amazon Web Services) has experienced a partial outage of their S3 platform. I’m lucky to be mostly surrounded by people that, at least in part, understand the nature of an internet outage. However, in these situations (included today one) I see people blaming the external service outage because it makes their platform to stop working.
So, this is the thing. You cannot blame anyone else but you if your platform stops working because an external service is down. If your platform stopped working is because of one of these two reasons:
- You don’t have a backup plan to execute when that service is down. Guess what. That’s your fault. No matter how redundant or stable a service is. Shit happens, and if you fully trust on the uptime of that service you are not very smart.
- Your platform heavily depends on the other service. It’s totally built on it and without it, your platform cannot exist. Assume it. If your business is about selling cupcakes at a school entrance and tomorrow the school is closed because a snowstorm you cannot blame the school. That happens. You just accept it.
Of course, you can and must consider SLA or any other warranties any service is going to give you. But that’s simple statistics based on known scenarios. Not everyone can create backup plans for everything for different reasons. That’s ok. But if you don’t have it you cannot blame other for your fault. Either you assume that it may happen or you just shut up.
I’m not even going to mention people that make fun of other services going down.