What prevents a new update to revert this or cause other safety problem?
Pushing updates in a rush is not a good sigh for critical software.
Pushing updates in a rush is not a good sigh for critical software.
What a coincidence! Car Full of Chaos Monkeys is the name of my Fountains of Wayne tribute band.
One would hope it's a culture of safety first at Tesla where all software changes are extensively reviewed, heavily tested in the real world and using whatever kind of simulations are possible, deployed in a reasonable manner to a small set of cars and only deployed to the main population of cars after a satisfactory amount of time.
> Pushing updates in a rush is not a good sigh for critical software.
Yeah, it's pretty scary to know the braking software in your car was tested for less than a week.
It's not like Tesla makes changes in production. They do it first in staging/test/SDDV/etc... like the rest of us.
If you have development experience you know that even trivial changes can cause unexpected issues.
Btw, why is braking and software connected, I am just curious how can you affect braking with an update, does this mean that a bug/crash will make the brakes not work at all or work not as good as a regular car.
If they uncover problems, why shouldn't they?
They should test them more, yes, as should probably all car manufacturers. And computer programmers. Complex bug-free software doesn't exist.
> also why did they not handle the issue before it caused bad PR, it is like they don't care as much for safety as others.
Most likely because they were not aware of the problem. When CR pointed it out, they investigated and fixed it.