It's hard to tell your boss that the IT department will do nothing after this incident (besides fixing it) and just hope that every further updates from crowd strike will be flawless. I'm sure some companies will stop using crowd strike, even if they have some multi year contracts. It's not a rational decision, but not having a drastic reaction to a drastic action just feels bad. Humans are bad at estimating such probabilities.
I didn't know this was still going around the internet. From a business perspective the airlines most affected should have had a contingency plan. Technology is a beautiful thing when it works. But when it doesn't hiccups can be mitigated by the company by just planning. I don't think this issue is something people should completely blame on IT. Every system has inherent risks due to human error, human judgment, and estimates are difficult the outcome could be unexpected. I'm glad that you clarified that it was a third party vendor to Microsoft. I thought it was just Microsoft which led me to think well if it is an update I doubt we will know really what happened because they are closed source. But I take it back. Sucks for them. It's just another business risk when you outsource a service to another company. I just don't think it would be realistic for people to think all updates or developments to be flawless. We also learn a lot from things not working. I did hear that Southwest airlines had a backup which was a legacy system unaffected by the update. This sounds like a good backup in this scenario that no one really could have predicted. Again, I wish I knew more of why the other airlines and airports didn't have some kind of contingency plan. I will have to look at it more later.
@@Simplyinfamous-yc4pi I think one component of this disaster is that the issue was related to a security software. For every other kind of software you could just postpone the update and work with the older version for a few days till the issue is either resolved or you know a fix. No one wants to run bleeding edge software, but you always want the latest virus definitions.
Just starting to watch (so maybe you will talk about it), but I really would like to know what went through the developers minds at the moment it was known. This, for me, feels like deadly 🥵😱
I kinda had this feeling once when cash registers for a customer of ours (some 15 years ago) went down over all of the Benelux. Luckily we had some backups in place. But I remember the initial panic very vividly. Imagine, the world seems to go down...
It's hard to tell your boss that the IT department will do nothing after this incident (besides fixing it) and just hope that every further updates from crowd strike will be flawless.
I'm sure some companies will stop using crowd strike, even if they have some multi year contracts.
It's not a rational decision, but not having a drastic reaction to a drastic action just feels bad.
Humans are bad at estimating such probabilities.
skip the pause where Christian runs up and down the stairs: 0:30:20
I didn't know this was still going around the internet. From a business perspective the airlines most affected should have had a contingency plan. Technology is a beautiful thing when it works. But when it doesn't hiccups can be mitigated by the company by just planning. I don't think this issue is something people should completely blame on IT. Every system has inherent risks due to human error, human judgment, and estimates are difficult the outcome could be unexpected. I'm glad that you clarified that it was a third party vendor to Microsoft. I thought it was just Microsoft which led me to think well if it is an update I doubt we will know really what happened because they are closed source. But I take it back. Sucks for them. It's just another business risk when you outsource a service to another company. I just don't think it would be realistic for people to think all updates or developments to be flawless. We also learn a lot from things not working. I did hear that Southwest airlines had a backup which was a legacy system unaffected by the update. This sounds like a good backup in this scenario that no one really could have predicted. Again, I wish I knew more of why the other airlines and airports didn't have some kind of contingency plan. I will have to look at it more later.
@@Simplyinfamous-yc4pi I think one component of this disaster is that the issue was related to a security software.
For every other kind of software you could just postpone the update and work with the older version for a few days till the issue is either resolved or you know a fix.
No one wants to run bleeding edge software, but you always want the latest virus definitions.
Just starting to watch (so maybe you will talk about it), but I really would like to know what went through the developers minds at the moment it was known. This, for me, feels like deadly 🥵😱
I kinda had this feeling once when cash registers for a customer of ours (some 15 years ago) went down over all of the Benelux. Luckily we had some backups in place. But I remember the initial panic very vividly.
Imagine, the world seems to go down...
validator misses empty file... nice.