I think you don’t understand the realities of software development. Have you ever tried to write an application that another person is going to use?
The software running onboard modern vehicles isn’t all from the vehicle manufacturer. There are computer parts in there from various manufacturers that have their own software, and all the various pieces have to interact. Bugs can show up later that didn’t appear in testing because no amount of testing can possibly check every interaction, it’s just too complex. And most of those bugs are relatively minor, things like the music player volume not adjusting properly, or a little lag time in the menus. The idea that every customer would bring their vehicle back to a dealer for an update that fixes something like that is ludicrously unrealistic.
I think the point the parent poster was making is that the system shouldn’t be designed that way in the first place. And when the vendor fucks it up due to releasing the product in a half-baked state, the hammer needs to be brought down on them in such a way that it will functionally discourage them from doing it again.
If the electronics providing functionality in your vehicle are so complex that the excuse is being made potentially adverse interactions between its various components from various OEM’s can’t be tested and accounted for, what has actually happened is that designed your product wrong. Throw it away, start over, and do it right next time.
the system shouldn’t be designed that way in the first place
Designed what way? Having parts from several manufacturers? Everything is designed that way. No manufacturer is an island, and having every manufacturer reinvent their own wheels is a terrible idea.
Tesla isn’t going to write their own firmware for every component that they buy from another company and no one sane would expect them to.
when the vendor fucks it up due to releasing the product in a half-baked state
There are so many assumptions about what’s going on in this statement that it’s hard to even begin addressing them. It is not possible to test any device that will be used in the real world in every possible set of circumstances that it might encounter. This doesn’t mean it’s “half-baked”, and it’s not an “excuse”, it’s just the nature of reality. Best you can do is test the most common circumstances.
I think you don’t understand the realities of software development. Have you ever tried to write an application that another person is going to use?
The software running onboard modern vehicles isn’t all from the vehicle manufacturer. There are computer parts in there from various manufacturers that have their own software, and all the various pieces have to interact. Bugs can show up later that didn’t appear in testing because no amount of testing can possibly check every interaction, it’s just too complex. And most of those bugs are relatively minor, things like the music player volume not adjusting properly, or a little lag time in the menus. The idea that every customer would bring their vehicle back to a dealer for an update that fixes something like that is ludicrously unrealistic.
I think the point the parent poster was making is that the system shouldn’t be designed that way in the first place. And when the vendor fucks it up due to releasing the product in a half-baked state, the hammer needs to be brought down on them in such a way that it will functionally discourage them from doing it again.
If the electronics providing functionality in your vehicle are so complex that the excuse is being made potentially adverse interactions between its various components from various OEM’s can’t be tested and accounted for, what has actually happened is that designed your product wrong. Throw it away, start over, and do it right next time.
Designed what way? Having parts from several manufacturers? Everything is designed that way. No manufacturer is an island, and having every manufacturer reinvent their own wheels is a terrible idea.
Tesla isn’t going to write their own firmware for every component that they buy from another company and no one sane would expect them to.
There are so many assumptions about what’s going on in this statement that it’s hard to even begin addressing them. It is not possible to test any device that will be used in the real world in every possible set of circumstances that it might encounter. This doesn’t mean it’s “half-baked”, and it’s not an “excuse”, it’s just the nature of reality. Best you can do is test the most common circumstances.