If there is a reasonable suspicion that the airplanes are not of considerable quality beyond rumours online and there is an honest intent to fix the airplanes rather than dispose of the ones that are deemed unnecessary, such a plan could certainly be executed over several weeks or months.
In this case, there is a major scramble to test every employee as quickly as possible by outsiders who have no idea how the company operates, what their standards are like, or what the problem space is about.
Barely self driving cars controlled by touch screens are almost entirely disconnected from a social media network other than that both employ programmers. Everything from the data processing location to the user interaction model is vastly different. The standards of quality of different components vastly differ; a UI bug in Twitter is far from catastrophic unlike a UI bug in your car, but a backend bug in Twitter can sink the business whereas a backend bug with Tesla can be annoying at worst.
I'm sure Tesla's developers are competent but the environment they operate in is completely different from the environment the people they review operate in.
At worst, the entire review produces no usable results because the Tesla developers don't have time to study the code base and validate any of the claims the devs make. At worst, the rushed reports are used to bypass layoff laws by providing a "reason" to fire people.
Either way, the end result is that the entire process is no more than pointless busywork for Tesla's people and has no real benefit to the Twitter code base.
Knowing Elon's intentions to fire half of Twitter but his subsequent retraction (probably advice from his lawyers because of layoff laws) I think it's foolish not to be sceptical of this entire event.
Code review can be a great tool to improve a business when it's done well; however, the rate at which things are progressing now indicates to me that this isn't done well.
In this case, there is a major scramble to test every employee as quickly as possible by outsiders who have no idea how the company operates, what their standards are like, or what the problem space is about.
Barely self driving cars controlled by touch screens are almost entirely disconnected from a social media network other than that both employ programmers. Everything from the data processing location to the user interaction model is vastly different. The standards of quality of different components vastly differ; a UI bug in Twitter is far from catastrophic unlike a UI bug in your car, but a backend bug in Twitter can sink the business whereas a backend bug with Tesla can be annoying at worst.
I'm sure Tesla's developers are competent but the environment they operate in is completely different from the environment the people they review operate in.
At worst, the entire review produces no usable results because the Tesla developers don't have time to study the code base and validate any of the claims the devs make. At worst, the rushed reports are used to bypass layoff laws by providing a "reason" to fire people.
Either way, the end result is that the entire process is no more than pointless busywork for Tesla's people and has no real benefit to the Twitter code base.
Knowing Elon's intentions to fire half of Twitter but his subsequent retraction (probably advice from his lawyers because of layoff laws) I think it's foolish not to be sceptical of this entire event.
Code review can be a great tool to improve a business when it's done well; however, the rate at which things are progressing now indicates to me that this isn't done well.