Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register
This site may earn commission on affiliate links.
I guess code reviews at twitter are going well so he’s reviewing v11 code next week?
Seriously, its not clear what he iss talking about here. Could be they put it in his car to check it - or he has a review scheduled with the team to go over the quality metrics before approving.

BTW, the Twitter "code review" looked more like high level architecture review I give to execs. Not really "code".
 
Seriously, its not clear what he iss talking about here. Could be they put it in his car to check it - or he has a review scheduled with the team to go over the quality metrics before approving.

BTW, the Twitter "code review" looked more like high level architecture review I give to execs. Not really "code".
Musk almost certainly is referring to reviewing the quality metrics, results from simulations, evaluation of telemetry from employee cars, status of specific problem areas, risk evaluation and recommendations from the development leads. Basically, ensuring that they have done their due diligence and everyone in charge agrees the software is safe enough to start releasing to 300,000+ vehicles.
 
Musk almost certainly is referring to reviewing the quality metrics, results from simulations, evaluation of telemetry from employee cars, status of specific problem areas, risk evaluation and recommendations from the development leads. Basically, ensuring that they have done their due diligence and everyone in charge agrees the software is safe enough to start releasing to 300,000+ vehicles.
I think you give him too much credit. He is going to drive it around and if he likes it he will give his thumbs up.
 
Musk almost certainly is referring to reviewing the quality metrics, results from simulations, evaluation of telemetry from employee cars, status of specific problem areas, risk evaluation and recommendations from the development leads. Basically, ensuring that they have done their due diligence and everyone in charge agrees the software is safe enough to start releasing to 300,000+ vehicles.

The question is, does he not trust the team to push the green button if the key metrics look to be better than previously-agreed-upon thresholds? Are they so borderline that he needs to sign off on the release after some debate? I’m suspecting there’s a lot of the latter given the long streak of shifted timelines. Or maybe they just have a regular weekly sync that he’s referring to and he’s making it sound unintentionally important when it’s just a routine thing.
 
  • Like
Reactions: impastu and DanCar
I think you give him too much credit. He is going to drive it around and if he likes it he will give his thumbs up.
In this case perhaps you are not giving Elon enough credit. There is a reason he has been so successful and it's not because he gives thumps up or down. From everything you hear he can be very detailed with staff. There may even be a conversation with the legal team.
 
Last edited:
I think you give him too much credit. He is going to drive it around and if he likes it he will give his thumbs up.
The question is, does he not trust the team to push the green button if the key metrics look to be better than previously-agreed-upon thresholds? Are they so borderline that he needs to sign off on the release after some debate?
A proper review process includes at least engineering review, business review and release review. No matter how crusty and cynical people have become about the history of delays, the idea that Elon is just a just a low-function salesman with no interest/capability to evaluate, seems absurd to me.

It's certainly true that there would and should be prior internal reviews within the team and with operational managers, Yet lt's pretty clear that Elon is close enough to this (very key) development activity that he would be involved in further review of something like v11 deployment.

The need for verification, validation and release review does not imply distrust of the development team; rather it implies a healthy process that gives team members, at many levels, a chance to step outside of their pressurized and potentially narrowly focused roles, organize their summaries and explain to a number of key people - including Elon.

I've seen good and bad review processes. The good ones reinforce healthy communication, reexamination from first principles, and bring new eyes to the problem. The bad ones evolve into a long checklist to avoid embarrassing repetition of past problems, without thinking holistically about why they really occurred. I will say that the more important reviews occur much earlier, when there's still time to affect the direction of the development. However, I see it as reassuring and not odd, that Elon would be involved at critical junctures.

Any commentary like this, that gives some credit to Elon and his process, will no doubt draw out the laugh emojis. It's fun to make cracks about his timelines and unreasonable optimism; I do it myself all the time. But all the same, I get a lot of enjoyment out of watching his very unusual companies from afar. You can't really explain how things work in inside by relying on car-salesman caricatures or the echo chamber of bitter internet rants from impatient customers.
 
The question is, does he not trust the team to push the green button if the key metrics look to be better than previously-agreed-upon thresholds? Are they so borderline that he needs to sign off on the release after some debate? I’m suspecting there’s a lot of the latter given the long streak of shifted timelines. Or maybe they just have a regular weekly sync that he’s referring to and he’s making it sound unintentionally important when it’s just a routine thing.
In every organization I have been associated with, the higher the stakes, the higher up the chain of command a decision goes.
 
Just a shout out to Elon - o/.

I'd take a peak in this forum anonymously on occasion if I were him. If so, I suspect he'd find this conversation amusing! 🤷🤷🤷

I moderate a small Tesla-related subreddit. And one day we received a DM from a Tesla employee saying:

"You’d be legitimately surprised where E lurks"

So you never know!