Live data from Hacker News

Former Tesla Firmware Engineer Discusses the System

twitter.com

291–300 of 589 posts

Re: Former Tesla Firmware Engineer Discusses the System

#291

> "the interior is a disaster, there's no instrument cluster which takes your eyes off the road" This is the most WTF aspect of the model 3 to me and seems to confirm that there isn't going to be some last-minute mitigation. I know it was done because autopilot was expected to be mature by the time model 3 rolls out, but I don't see how it can even be street-legal when you need to look away from the road to determine…

Customers seem to love it.

Re: Former Tesla Firmware Engineer Discusses the System

#293

Earlier quoted context omitted.

Only naive ppl blame the language instead of the codes based on the language.

Some languages are unfit for certain purposes. For example, Python is not meant for low-level programming, and C is not meant for writing secure, mission-critical applications.

Furthermore, some languages tend to attract less skilled programmers, in part due to having lower barrier of entry and requiring less domain knowledge for being able to crank out something functional, quickly.

Re: Former Tesla Firmware Engineer Discusses the System

#294

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…

Only naive ppl blame the language instead of the codes based on the language.

> Only naive ppl blame the language instead of the codes based on the language.

A language is a tool, and like any tool it can be badly designed and/or unfit for certain purposes.

Re: Former Tesla Firmware Engineer Discusses the System

#295
post #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 dangerousl…

"Fleet" is longstanding car industry lingo. Not something Tesla dreamed up to keep you under their boot.

Source: Father worked in car industry. All of my neighbors, too. Pretty much everyone I knew and then, eventually, me... albeit tangentially.

Re: Former Tesla Firmware Engineer Discusses the System

#296
post #64

Earlier quoted context omitted.

If the infotainment system caused the MCUs to reboot while someone traveling "130mph on San Mateo Bridge" and that caused the break system to segfault due to unconventional way of loading parts firmware, it might be a life&death situation, easily. Examples in that threads go on, literally hundreds!

There’s no concept of “reboot” with MCUs, since there’s usually no OS. Likewise there’s usually no concept of segfault, because segfault requires memory protection which is something most MCUs don’t use.

Tesla’s MCU runs Linux. Older ones use a 2012-era Nvidia mobile SoC, while newer ones use something from Intel.

Re: Former Tesla Firmware Engineer Discusses the System

#297

Earlier quoted context omitted.

> Why Linux instead of an RTOS? Same reason SpaceX eschews radiation-hardened processors for redundant off-the-shelf cores: supplier competition. There aren't many RTOS engineers on the market; there are many Linux engineers. Once they got over the cost of hardening the kernel, SpaceX found itself at a scaling advantage versus RTOS-based competitors.

Not just that but holy shit some of those commercial RTOSes have major issues. I work in aerospace and we recently used one where the whole system would crash after ~230 days of uptime. At least with Linux you're getting a system that's been used so much that all major issues like that are ironed out. Nothing beats a few million testers.

Million? For linux perhaps billion :)

Re: Former Tesla Firmware Engineer Discusses the System

#299
post #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 dangerousl…

"Fleet" is longstanding car industry lingo. Not something Tesla dreamed up to keep you under their boot. Source: Father worked in car industry. All of my neighbors, too. Pretty much everyone I knew and then, eventually, me... albeit tangentially.

""Fleet" is longstanding car industry lingo. Not something Tesla dreamed up to keep you under their boot."

I am aware of that and I hear that terminology used by rental car companies and equipment dealers, etc.

My objection is to what I hear as a subtle difference - the post-sale automobile to a private, end-user is still referred to as belonging to their fleet - as if one's ownership and use of the car were a minor detail.

I dislike this subtle shift in language and attitude.

Re: Former Tesla Firmware Engineer Discusses the System

#300

Earlier quoted context omitted.

On a tangent, but still germane to the thread: Why arent their efforts to create "autonomous only" traffic managment scenarios, where people drive into a given, known area, and the area then takes control of managing the traffic and vehicles. Such that you relinquish control of the vehicle to that area's control system, with your destination stated and then your vehicle is managed accordingly. For example, a parking…

That seems to match the right tool (AI driving) to the right job (well-defined, well-controlled situations). I seem to recall that similar ideas go back to the early 1990s, at least, for highways: Drive your car to the entrance ramp, plug in your destination, and the autonomous system takes it from there. But for many of these things, such as the Bay Bridge or a highway, it seems like there is a simpler solution: Put…

Ive been picturing the rail problem for some time as well.

Not just for cars, but also for cargo... just have a constant gondola-like conveyer that detaches a platform from the line to slow it enough to allow for cargo to get on, then re-zip-it backinto the line and speed it along, de-rail it once it hits its exit/location...

ideally though, in cities, there would be no surface streets and all cars would have their own level below that of bikes pedestrians.

What would SF look like if a superstructure was built above all streets and all pedestrian and bike traffic was moved up there? (sure, SF may be a poor example, so just select [city])

Look at Singapore's vast underground connecting malls between facilities. Those are pretty amazing.

I grade US urban/city planners rather poorly.

Post reply on HN