I think it also just took on a bunch of technical debt and was poorly managed, so I don’t know if they could have pulled it off with more time. Like they were forced by management to use KSP1 code, and were not allowed to talk to the KSP1 devs, and repeatedly hemorrhaged workers meaning even less of the code base has experts. I think they maybe would be better off starting from scratch (reusing assets) at this point if they wanted to deliver their more difficult goals like multiplayer.
I get where you are coming from, but this event is pretty much entirely the fault of Crowdstrike and the countless organizations that trusted them. It’s definitely a show of how massive outages are more likely when things are overly centralized and proprietary, and managed by big, shitty, profit driven organizations. Since crowdstrike operates in kernel space, it doesn’t matter which operating system it’s on, it can break it if it does something stupid. In fact they managed to break some redhat machines not too long ago, and some Debian machines not long before that. It’s just the impact wasn’t as far reaching as this recent utter fuckup, just because fewer critical machines were affected, so we didn’t hear about those smaller fuckups in the news.