Nah I like the term recall. Just because the fix is “easy” doesn’t mean the product wasn’t broken. Automakers should take the software in their cars seriously especially the ones that market their cars like a cell phone.
Broken software shouldn’t be accepted as much as it is. Especially in safety critical systems like cars, especially when they remove manual controls for things like steering, brakes, hand brakes and door handles. Fly/drive by wire is more dangerous when the software is unreliable. Mechanical linkages fail immediately or take a long time. Bad software fails in uncertain and potentially chaotic ways.
I just think it’s useful to have different words for things that can be easily fixed without having to go get the car to a mechanic and having no immediate safety impact, and things that may require you to take the vehicle to a mechanic ASAP because there is immediate serious danger. They should not be in the same category, and people should be aware that they require different levels of attention and urgency. When it’s all just referred to as a “recall”, people will start to not take them seriously when they more often than not are minor things like this.
It’s not useful at all, knowing which brand sells shitty cars that have major issues is a good thing, this whole attitude that you can do OTA fix something therefore it’s fine and we can ship bad product is fucking ridiculous attitude to a multi-ton weapon capable of killing multiple people
It’s worse than that, people will argue shipping good code is impossible. Good testing is hard, so it’s avoided for things like unit tests. Something that’s only equivalent to basic QA in manufacturing. Every software functions is a design change and the system needs to be fully validated and tested. That’s means driving the car, and not shipping the code and using the users cars to prove your design.
The problem is, and of course when it matters I forget the specifics, that there are many times when language is changed to soften how bad something is and it results in people not taking things seriously.
The issue here is cars being shipped in a broken state, that’s it. They recall the vehicles and force people to skip out of work or whatever to get this shit done because their products suck, and if they wanted to not deal with that then maybe they should products that don’t suck. They can also collect a bunch of these issues, seeing as they’re common, and either make a patch of several minor issues or just say that the problem will be addressed at the next service. This is entirely on the companies to save their image, not us to change our language to make them feel better.
Nah I like the term recall. Just because the fix is “easy” doesn’t mean the product wasn’t broken. Automakers should take the software in their cars seriously especially the ones that market their cars like a cell phone.
Broken software shouldn’t be accepted as much as it is. Especially in safety critical systems like cars, especially when they remove manual controls for things like steering, brakes, hand brakes and door handles. Fly/drive by wire is more dangerous when the software is unreliable. Mechanical linkages fail immediately or take a long time. Bad software fails in uncertain and potentially chaotic ways.
I just think it’s useful to have different words for things that can be easily fixed without having to go get the car to a mechanic and having no immediate safety impact, and things that may require you to take the vehicle to a mechanic ASAP because there is immediate serious danger. They should not be in the same category, and people should be aware that they require different levels of attention and urgency. When it’s all just referred to as a “recall”, people will start to not take them seriously when they more often than not are minor things like this.
It’s not useful at all, knowing which brand sells shitty cars that have major issues is a good thing, this whole attitude that you can do OTA fix something therefore it’s fine and we can ship bad product is fucking ridiculous attitude to a multi-ton weapon capable of killing multiple people
It’s worse than that, people will argue shipping good code is impossible. Good testing is hard, so it’s avoided for things like unit tests. Something that’s only equivalent to basic QA in manufacturing. Every software functions is a design change and the system needs to be fully validated and tested. That’s means driving the car, and not shipping the code and using the users cars to prove your design.
The problem is, and of course when it matters I forget the specifics, that there are many times when language is changed to soften how bad something is and it results in people not taking things seriously.
The issue here is cars being shipped in a broken state, that’s it. They recall the vehicles and force people to skip out of work or whatever to get this shit done because their products suck, and if they wanted to not deal with that then maybe they should products that don’t suck. They can also collect a bunch of these issues, seeing as they’re common, and either make a patch of several minor issues or just say that the problem will be addressed at the next service. This is entirely on the companies to save their image, not us to change our language to make them feel better.
But recall meaning you call the products back, so they can be fixed, or not? This seems not the case here, just a safety relevant bugfix…