I agree, but what I don't get is how after all that planning they could post a new map with multiple errors and omissions. Either someone is very sloppy and should be fired, or they are testing to see how many owners react to the removal of what they consider to be "marginal" locations.
Fired? Really?
Tesla is moving fast. They are pushing on many fronts. They are acting with agility. They are undertaking an enormous challenge the likes of which has Never. Been. Attempted. They give every indication of caring about their customers and trying to do 'what's right' while balancing a significant number of other obligations.
When's the last time you've dealt with a company who's CEO accepts and answers email from individual customers and adjusts product plans accordingly? (I have one from Elon in my inbox where he did just that). When's the last time you've seen a CEO speak frankly in his blog as is the case with Tesla? When's the last time you've had a company say "We believe in our product so much we'll extend the warranty to accidental battery damage outside of our control"?
Now does that mean they are perfect? Obviously not. But they are working to avoid the slow behemoth-like movement that other major companies exhibit. I suspect in many cases we are hearing about some things almost real-time. Oh and by the way, little things like car fires and NHTSA investigations might be a bit of a distraction as well.
What does all this have to do with your post? You assume that the map omission was deliberate on the part of the supercharger team in to see if they could get away with a reduction of sites and our reaction, or such an egregious omission on the part of the web content management team, that somebody should be fired. I'll give you option #3: things are moving fast and furious within Tesla and there was a fumble between teams.
I've been in IT for nearly 25 years. If you think that it's unreasonable to EVER deploy the wrong file from source control, power up the wrong system, accidentally copy the wrong file, aim at the development DB rather than the production DB, etc... then you must be a fun guy to work with.
Should they learn from their mistakes? Yes. Can they improve on QC in communication? Sure. Does the web guy deserve to get fired for deploying the v2.01 version of the content instead of the v.2.02 that was checked in at 2am that morning? I hope not. Especially when we have a company responsive enough to answer the email within hours, and get a correction up shortly thereafter.
Last edited: