Is risk management 101, I'm sorry if you don't understand but I don't have time to explain it to you.
If 100% of your business is based in a country that has been threatened to be invaded many times and also had been attacked 8 years ago and you still think is ok go have 100% of your engineering and core business there then is your problem.
You don't know what Risk management? Business continuity?
Is the same reason why you don't deploy your DB in one PC in your basement and hope that nothing happened. If you get flooded and you didn't have a plan to recover is your sole responsibility.
Are we talking about the risk of the company being entirely destroyed, or the risk of it being made inconvenient for them to serve Russian customers? I figure this thread is about the second one since those are the consequences that are happening now. If they don't particularly need Russian customers to survive, it doesn't seem like they made a mistake in not preparing against that risk more.
I'm talking about the first, doesn't seems to hard to understand isn't it?
To me the move is like: "well now I've no way to do by business because my engineering and the core team is under bomb shelter, so lets ban the Russian customers because I'm pissed"
They can do that if they're happy with it, I'm with you on this.
If 100% of your business is based in a country that has been threatened to be invaded many times and also had been attacked 8 years ago and you still think is ok go have 100% of your engineering and core business there then is your problem.
You don't know what Risk management? Business continuity?
Is the same reason why you don't deploy your DB in one PC in your basement and hope that nothing happened. If you get flooded and you didn't have a plan to recover is your sole responsibility.
The same goes business wise