Todd Burch
14-Year Member
With so many shared parts between 3 and Y, and even some in the Semi (like the motors), it is likely the costs of the 3 will drop even further when Y and Semi enter production.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Tesla made the Model S/X refresh announcement on 4/23, which was 1 day before they released Q1 earnings which I think most here would agree were way worse than expected (even with 200m in credit sales).
To me it seems likely that the announcement was moved up a bit before the manufacturing lines and or supporting supply chain (motor manufacturing in Giga1) were ready to go. Given the huge drop off in S/X demand in Q1 that was probably a smart move.
I'll be sure to take that into consideration. Thank you so much for your kind advice. lolForbidden topic
These things are subjective, obviously, but whatever problems there are with Tesla’s UI, it’s far and away better than any other auto manufacturer’s(or 3rd party equipment provider’s). In fact, it was just rated as such by Consumer Reports. It’s not even close.
Thanks for the info. I guess they've lost all the people who are good at the job, perhaps due to Musk's mismanagement.Yes, but it's a super small team of a dozen designers or so, based at Tesla Design in Hawthorne. Keep in mind that they're not only in charge of all the MCU UIs but also the Tesla website, the app, etc.! The team size is maybe a 1/10 or 1/20 of what it actually should be, compared to FB, AAPL, GOOGL, MSFT …
Thanks for the picture. It does sound like a toxic, broken working envrionment with incompetent bosses.From what I've heard, people are overworked, tired and fed up with the fact that they're reporting to either Franz or Elon – neither have much clue about UI design. The modus operandi is a toxic, top-down "We want to ship feature X so you better make it work SOMEHOW" approach.
Was he the one who designed the original Model S UI, which was actually very good, before it got repeatedly downgraded and broken in "updates"?Their poster boy, Andrew Kim, left in December '18 to work for Apple. He was in charge to revamp the Model S/X interface for the M3 and Semi.
Not "all" but "most"This is total nonsense. You're suggesting not only that there is zero price elasticity to all the things we import from China,
Not true for all the things we import from China...but that they are also a monopoly producer with no alternative suppliers globally to what they produce.
I am sure they don't, at least not in the UI department (Autopilot is separate). They used to. They don't any more. Those people left. Why? How were they mistreated?It's a common myth among those who don't know anything about software development that just adding more people will solve your problems. Nothing could be further from the truth. In fact adding more people beyond a certain amount can greatly slow down development and create less good solutions. Small teams of 4-8 people work best in my experience...if they are all top notch. In fact there is an inverse relationship between number of coders and time-to-delivery/quality-of-code once you get above a certain threshold.
Another thing people don't understand is that one excellent coder is worth more than 5 OK ones. The excellent one will be able to do things that none of the other 5 coders could do...in fact things that maybe 500 OK ones couldn't do. And they will do it better and in a cleaner way so it runs fast and can be more easily maintained. The job as a manager is to find these people, treat them well and keep them. Also to challenge them else they get bored. But finding them is very very hard. I am sure tesla has some of these top notch people.
But these excellent coders are not designers usually. They are good at "designing" code, but not end user solutions. That's a different skill set and in fact is also very hard to do. Often the trick is doing very hard things but obscuring the complexity of that behind the scenes so the end user experience is clean and as-easy-as-possible. This can be very very hard to do given complex requirements. It's also the reason most software sucks...bad design.
Implement what the CUSTOMERS want.As far as the "We want to ship feature X so you better make it work SOMEHOW" approach.". That's their job. Not sure what is at issue here. Management wants some feature and its the staff's job to design and implement it and to do it well. What else are they supposed to do?
Electric Mercedes Benz doesn't scare the bejezus out of Toyota nor Detroit.
You need a compelling $25k CUV/hatchback and a compelling $35k Pickup for that.
BUT this is not the issue with the Tesla UI team, I can assure you, knowing people first hand that worked for and with them:
They are simply overworked und understaffed for the amount and scope of their work they have to deliver.
This is not general assembly where you can add a few hours of physical labour that you can sleep off the next day. Designers and engineers are productive for what, 4-6 hours net per day? Beyond that, they produce garbage and garbage only. Garbage that has to be fixed eventually. Letting them work 60h+ a week doesn't result in more amazing code or design, it results in more subpar work you can trash the other week.
Letting people work to a point where they fall asleep during mission-critical meetings – as I was told – is not a sign of great work ethics but rather of weak ass management.
There is no reason, no ****ing reason, why they shouldn't hire another 10-30 designers. There's a difference between being "spartanic" and "idiotic" and as things are right now, the Tesla UI team setup is clearly in the "idiotic" category – hence why design superstars like Andrew Kim are leaving.
Tesla/Elon really screwed up with Model 3 costs, which appear to be $38,000 for cheapest model.
Which would you choose?
1) A car codebase with 100% coverage of unit tests with access in the field only via the on-board diagnostics (OBD) port.
2) A code base with some sensible pre-launch tests, but not 100% coverage though the code is instrumented, the car does wireless reporting, driver instructions may be changed, and OTA updates are readily done.
Team and business. Not the same. (One could argue Azure's success is driven by installed customer's base lock-in effect and smart business policies, rather than quality of the offer. I know I almost chose them, agains my will for a few $M/year spend. Because of how they were offering free builds and compute time, and ease of integration into our eco-system...)
But further, it's been tumultuous couple years on software self-driving side. I've hoped that team was settled by now, right people are in charge, and they have teams that works amazingly well together.
Elon feeling need to take control and shuffle things around, whether it turns out good or bad, tells me things are not great. They may be ok, good even, but not great. And that's disappointing, as software was one area to take comfort in,
after pressure coming from production, cell capacity, margin and demand concerns. To anyone that has none of these concerns, good for you - you can't ease my concerns no matter what you say, until I see Tesla's results that debunk them.
#1 is also more problematic in a rapidly evolving code base, which I gather Tesla has. #2 can be fine but still need to test the hell outta it one way or another before going GA.
the problem for Tesla, and frankly most software projects, is that the initial code base does not consider all that will be added over the next 20-30 years because you don't know what you don't know. So if you take the quicker easier path short term your foundational architecture quickly ends up not being flexible enough so to meet the next, newest feature add-ons you end up bolting them on in what I will call inelegant ways to meet timelines instead of re-architecting to plan for expansion over time and the code base becomes shitty.
This is the bain of almost all long term code bases and interfaces. The feature explosion ends up making the user interface unwieldy and the code base a pain to maintain. Very few product architects plan well for this starting from release one onward. I have no inside knowledge of tesla to say whether they did it right or not.
Having worked for Apple doing software, as well as many other top companies (Silicon Valley and elsewhere), I can state with absolute certainty that every single team was always overworked and understaffed, often egregiously so. So what?
Implement what the CUSTOMERS want.
There's a disconnect between management and customers right now.
And China offered Musk permanent residency.It sounds like there was a cost to go from 7k to 10k. Plus, they don't have the battery supply anyways to feed Fremont to that level. As evidenced by Panasonic's recently disclosed info.
Seems like China was the smart play considering all the problems in the USA. China rolled out the red carpet for Tesla. Readily available supply of batteries in China. Chinese loans for the factory. Rapid construction for a factory they were always going to build anyways.
It was a fast and smart course correction, and that's one thing Musk has been very good at in the past.At least they course corrected in a way that's continues their growth.
Perhaps they mistakenly invoked the squirrel prediction NN.
I'd just like the USB media player to work as well as the off-the-shelf software which I can get for free on my computer. This is, seriously, the work of a couple of weeks, and I could do it myself in that time, and there are hundreds of people complaining about it. And it's just flat out embarassingly bad.That would be a different issue.
Really though knowing what customers want is not a problem, you know the saying about opinions are as numerous as...Tesla users are vocal and not shy about giving their opinion. Plus thousands of Tesla employees drive Tesla's and have ideas too. But what neroden wants may be very different than what evnow wants.
Basic functionality comes first. Tesla's been failing at that.The trick as a manager is to figure out what in fact makes the most sense to deliver out of the sea of options before you,
Yeah, and neither did anyone else.So are you saying you didn't request fart mode as being very important?