8 ms·
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.
by simion314 8y ago
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.
- colinbartlett 8y agoI'd like to think they have some kind of automated CI with a huge warehouse full of cars that automatically drives around and tests everything with each Git push.
- super-serial 8y agoAnd it's a demolition derby where only the cars that survive get to pass on their genes/settings to the next generation on the production line.
- psychometry 8y agoThe cars are full of actual chaos monkeys.
- reaperducer 8y ago>The cars are full of actual chaos monkeys. What a coincidence! Car Full of Chaos Monkeys is the name of my Fountains of Wayne tribute band.
- jonknee 8y agoThey sort of do, it's the general public.
- empath75 8y agoAnd they've only killed a few people so far.
- cjhopman 8y agoIf they did, they wouldn't need the media to find the problems for them. Without CR reviewing every update, how confident can you be that they won't regress the braking?
- carbonatedmilk 8y agoThis image delights me. "Jenkins, hit the track!" "Immediately, Sir."
- reaperducer 8y agoPlease cite your evidence that this was done in a "rush." It's not like Tesla makes changes in production. They do it first in staging/test/SDDV/etc... like the rest of us.
- simion314 8y agoA feature landing a few days after Elon Musk asked for it, how much testing/miles was this actually tested? If you have development experience you know that even trivial changes can cause unexpected issues.
- reaperducer 8y agoI've had development experiences involving "all hands on deck" overnight testing of an upgrade if the boss thought it was important. Does that count?
- simion314 8y agoYes, me too, and adding a new thing in a rush because the boss wants it today it usually involves hacks, ugly workarounds, incomplete functionality. Also putting a fix late in the day increases the chance of making mistakes. 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.
- donarb 8y agoAlso in response to an unfavorable review from a magazine. Is Tesla going to push out fixes after a wave of critical tweets?
- fmihaila 8y ago> Is Tesla going to push out fixes after a wave of critical tweets? If they uncover problems, why shouldn't they?
- simion314 8y agoThey should test them more, 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.
- fmihaila 8y ago> They should test them more, 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.
- simion314 8y agoDo you think they are other safety related issues that they are not aware and they are waiting some big negative PR until they notice(people reported issues in the exact place the Tesla killed the driver but was not enough)
- intherdfield 8y ago> What prevents a new update to revert this or cause other safety problem? 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.