Live data from Hacker News

Former Tesla Firmware Engineer Discusses the System

twitter.com

191–200 of 589 posts

Re: Former Tesla Firmware Engineer Discusses the System

#191
The most disturbing part of this, for me, is this line in the very first tweet:

"... caused almost the entire fleet to reboot loop ..."

I am not interested in being part of someone's fleet. The fact that they use this language at all to describe an end-user who has purchased an automobile suggests that their expectations and my own - of what it means to purchase and operate a car - are in deeply (possibly dangerously) mis-aligned.

Re: Former Tesla Firmware Engineer Discusses the System

#193

Earlier quoted context omitted.

I think this is a naive perspective. I've heard many similar stories from friends that work in the German automotive industry, and I think you would be surprised how many payment systems are tied together (e.g. (insecure) FTP servers to sync daily payments). Every organization has these types of things internally. As an engineer, I don't like it, but it's a fact of life.

Banks can reverse transactions if they want to. Tesla's cavalier attitude towards manufacturing has yielded a 14% first pass through rate on the Model 3 line (which is abysmal and may bankrupt the company along with declining M3 demand) vs. the industry standard of ~80% FPT rate. Source - https://www.businessinsider.com/tesla-hit-model-3-target-by-... We're at the point in the Tesla story similar to that of 2008 wher…

Why are so many things framed by HN users in terms of scenes from The Big Short?

Re: Former Tesla Firmware Engineer Discusses the System

#194

I used to work at SpaceX on the team that did a piece of software called "WarpDrive". It was a massive monolithic ASP.NET application, with large swaths done with ASP.NET WebForms and a slow frontier of ASP.NET MVC gradually growing when I was working there. This application was responsible for practically everything that ran the factory: inventory, supply chain management, cost analysis, etc. Elon is a big Windows f…

I used to work at SpaceX on avionics software, in a role very similar to OP, and my experience was similar in some respects. The tech and products were complex. The turnover rate was high and training new hires was a lengthy process. The new projects coming down the pipeline never ceased (this was during a period where FH/F9-1.1/Dragon/Crew was all under design/development and constant iteration). It was fun for a yo…

I heard the same thing about the burnout and turnover. Do companies really think they are saving money by paying peanuts, grinding people down to burnout, and then constantly having to rehire/retrain new people as the old ones leave? Meanwhile the code is a mess because nobody has been there longer than a year and there is no architecture or design continuity. Just frantic patches over other frantic patches by burnt out junior engineers. It makes no sense!

Re: Former Tesla Firmware Engineer Discusses the System

#195

Earlier quoted context omitted.

> Tesla’s infotainment and IT infrastructure is unrelated to their safety. Only if it's deliberately isolated in the vehicle. It should be. Aaaand, it isn't: the firmware upgrades to all other car computing elements go through it.

Runtime isolation is distinct from compile/build-time isolation. You're citing the latter, but it's the former that matters. Tesla gets this right, e.g. an interrupt in the MCU does not have any effect on braking, drive-by-wire, or ADAS systems while a car is in operation.

Fair enough, but if those bits pass through the infotainment center on the way in, controlling one allows you to control the other.

Re: Former Tesla Firmware Engineer Discusses the System

#196

Earlier quoted context omitted.

Yes, but he's already marked as "former", so recovery is limited. See the Waymo lawsuit.

So, after separating from company, you can release all proprietary information and you'd have limited liability? I thought there would be larger recourse. Not familiar with law though.

If he is revealing gross misconduct it could be consider whistle blowing.

Re: Former Tesla Firmware Engineer Discusses the System

#197
post #58
post #31

Earlier quoted context omitted.

Not sure if you're being sarcastic or not, but the Toyota issues were not caused by any software bug. Most cases were caused by people hitting the wrong pedal. The others were caused by floor mats that were a bit too long, causing the gas pedal to stick. https://www.caranddriver.com/features/its-all-your-fault-the...

Regardless of whether the acceleration were caused by the software or not, the testimonies for the software experts called in to review Toyota's source code for the case were eye-popping: http://www.safetyresearch.net/blog/articles/toyota-unintende... > Skid marks notwithstanding, two of the plaintiffs’ software experts, Phillip Koopman, and Michael Barr, provided fascinating insights into the myriad problems with To…

When you're paid to find errors in software, you point out every conceivable bug you can see.

Re: Former Tesla Firmware Engineer Discusses the System

#199
post #8

Why is this interesting or surprising? Of course almost all challengers have hacky tech under the hood because they don't have the resources. Winning from that position is possible not because of generally better tech but by delivering something that the incumbents don't. Remember the demo of the first iPhone (vs the huge expertise of Nokia). Or how Microsoft won the desktop starting from a single user, cooperative m…

> Why is this interesting or surprising? Of course almost all challengers have hacky tech under the hood because they don't have the resources First, we're talking about a multi-billion dollar company here (they've raised ~ 15 B), not some small "challenger". Second, your example is the iPhone and Facebook. Those don't have the potential to kill their owners or run over people.

That’s what it takes to be a challenger in that space. For example, most biotech series As are $100M, because that’s just what it takes to compete (but/lease equipment etc.).

Re: Former Tesla Firmware Engineer Discusses the System

#200
post #83
post #8

Why is this interesting or surprising? Of course almost all challengers have hacky tech under the hood because they don't have the resources. Winning from that position is possible not because of generally better tech but by delivering something that the incumbents don't. Remember the demo of the first iPhone (vs the huge expertise of Nokia). Or how Microsoft won the desktop starting from a single user, cooperative m…

Remember Theranos? For every good success example, there is a good failure example.

Theranos never had a real product or sales and was a fraud from the beginning of institutional investment. Comparing them to Tesla is pointless and has been done to death.
Post reply on HN