2 ms·
>I hope you don't do anything for a living that involves risk mitigation (I suspect you do not...) Quite the opposite, I have worked a long time very closely w
by colechristensen 5y ago
>I hope you don't do anything for a living that involves risk mitigation (I suspect you do not...)
Quite the opposite, I have worked a long time very closely with reliability and have done no small amount of time studying failure. Everything fails sometimes, there are always unknowns that aren't accounted for.
>It's like saying "who cares if there's an hour a year that my car doesn't work?"
This is often the case? Oh no, you have a flat tire, a dead battery, or whatever. It's not world ending, get to your destination another way or reschedule.
>Can you visualize how someone can blow a multi-million dollar sales presentation because a key piece of data doesn't reach them in time? Do you consider that acceptable risk?
If millions of dollars are on the line and you can't figure out how to work around a simple communications issue, you deserve to lose the deal. Not being able to handle failure or insisting on 100% uptime for dependencies is a sign that you have no idea how to handle risk.
- xyzelement 5y ago> Not being able to handle failure or insisting on 100% uptime for dependencies is a sign that you have no idea how to handle risk. Like I said 8 messages up this thread, I agree that people should have more resilient methods for handling these needs, the point is that this is often not existent.
- colechristensen 5y agoPeople don't have text messages, phone calls, messaging apps, in person conversations, USB thumbdrives, somebody else's email at a different provider... you're not a brain in a vat connected to the universe with email, you can figure out how to communicate without it for a while if it goes down.