Isn't it on Reddit? Here: https://www.reddit.com/r/EnoughMuskSpam/comments/99sbwa/form...
It's on YOSPOS originally.
Former Tesla Firmware Engineer Discusses the System
231–240 of 589 posts
Re: Former Tesla Firmware Engineer Discusses the System
#232Earlier quoted context omitted.
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…
Capitalism. Need for money and results. I don't think that anybody wants to burnout anybody, it's just the pressure of the whole system I guess. Money pushes to do things fast. Shareholders and clients to keep happy.
Burning out people at large rate is not effective and persistent crunch is contraproductie. It is less of capitalism and more of wishfull thinking combined with wish to be seen as tough manager.
Re: Former Tesla Firmware Engineer Discusses the System
#233Earlier quoted context omitted.
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.
248 days of uptime by any chance? edit: I saw the same on a fleet of thousands of JVMs which hung on 100% CPU after 248 days very consistently. Closest thing to an explanation I ever got was perhaps it is storing uptime in hundredths of a second (why not ms???) in signed 32 bit integers, see: https://ma.ttias.be/248-days/ In the end we solved it by restarting with a cronjob between 2am and 4am after 247 days...
One thing to look at is the sum of Anonpages if you have THP enabled. That was enabled by default after CentOS6.2. The usage itself isn't an issue, but there is a known memory leak in THP and the fragmentation can get wedged after a couple hundred days based on usage characteristics of the server.
Re: Former Tesla Firmware Engineer Discusses the System
#234I 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…
What's wrong with ASP.NET? It might not be the most sexy framework out there, but it's great for this sort of thing - there's a huge business application ecosystem surrounding it.
While that may be true, a huge monolithic system that does everything is seldom great.
Re: Former Tesla Firmware Engineer Discusses the System
#235I 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…
>Elon is a big Windows fan and pushed hard to run the whole shop on Microsoft tech wow - this is surprising to me and wasnt mentioned in the biography - any ideas why ?
Yeah it was (Ashley Vance book), he chose Windows over Linux when developing PayPal back In the day because the tooling in Windows was far more advanced (visual studio IDE) due to the parallel games industry driving development on that platform
Re: Former Tesla Firmware Engineer Discusses the System
#236Earlier quoted context omitted.
This is OK if you can guarantee 100% separation of concerns, but the news reports where hackers were able to take over control systems in the car through bugs in the entertainment system should be a huge note of caution.
I mean the entertainment system ideally should not be connected to the engine/drive train systems. That would be a risk management strategy.
There is difference between entertainment system and infotainment system.
Infotainment systems are increasingly used as primary UI for almost anything on car that is not controlled by steering wheel and pedals and thus has to be able to communicate with almost everxthing that is in the car. Tesla is pretty extreme example of this, but it works this way for most manufacturers.
Re: Former Tesla Firmware Engineer Discusses the System
#237I do not want a car that someone I've never met can "ssh" into, or any other remote access method. Think I will be holding on to my ten year-old car as long as possible.
You're still going to be sharing the highway with them.
Re: Former Tesla Firmware Engineer Discusses the System
#238Earlier quoted context omitted.
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…
Capitalism. Need for money and results. I don't think that anybody wants to burnout anybody, it's just the pressure of the whole system I guess. Money pushes to do things fast. Shareholders and clients to keep happy.
The question of course is whether the high turnover actually is the most efficient way—you're spending far more employee time training them (both learning the company's approaches at a high level, the problem space, and their way around the code base) than you would if you had higher retention.
While you might need to pay more and improve working conditions, would you be more efficient given the individual staff would spend more time being productive?
Re: Former Tesla Firmware Engineer Discusses the System
#239Do NDAs really just expire after three years like this ex Tesla employee claims? Something tells me that he will be sued very soon.
Re: Former Tesla Firmware Engineer Discusses the System
#240Earlier quoted context omitted.
Not sure if you’re trolling or not. Well played
I have some good news for you - we have invented these things called "jokes", in which people make statements about things that are obviously untrue as a means to elicit a humourous response in the reader. Now you too can go forth with this knowledge and be prepared for a world in which people aren't saying obviously untrue things solely as an attempt to trick the uneducated and gullible into believing falsehoods! Go…
I have some good news for you. There is a place where that type of humor is appreciated. That place is Reddit.