>>56803600I wanted to take a quick moment to mention something about this
You know how some companies test their employees retardation by hiring a company to setup those fake phishing emails, and if you fall for it twice you get fired (or some similar kind of punishment for cnsistent failing it). One buddy of mine told me the failure rate of their company was 80%, meaning only 20% of the 400 people hired passed and didnt fucking fall for it.
Upon being shocked at this astounding failure rate, the company that administers this test said "oh that's actually a better result than most companies, you did a good job"
Just think about that for a moment, 80% failure rate is considered good, meaning other companies are almost always going to fail this for every employee who is tested. All you have to do is not click a suspicious email, or attachment, or link and 80% or more fail this. It reminds me of the Google employee that fell for one, took to twitter to say its not their fault because "It looked so real" no bitch you work at fucking google how in the world are you this bad at spotting phishing emails.
As for the internal structure of the company I will assume a few changes but only because there is no way to guarantee it. They may change how permissions per employee works but they will still have someone central to it all maintaining it all. They will absolutely redo a lot, but anything released may be unchanged, just moved. Any in-development stuff will be modified on its passwords or storage solution
