I think this point from the post deserves emphasis, for consideration in future discussions:
> If Tesla makes a "major" change to software, pretty much all bets are off as to whether the new software will be better or worse in practice unless a safety critical assurance methodology (e.g., ISO 26262) has been used. (In fact, one can argue that any change invalidates previous test data, but that is a fine point beyond what I want to cover here.) Tesla says they're making a dramatic switch to radar as a primary sensor with this version. That sounds like it could be a major change. It would be no surprise if this software version resets the clock to zero miles of experience in terms of software field reliability both for better and for worse.
I am admittedly a broken record on this point, but Tesla moves very fast and very nimble on a system that is under design controls. It would be very educational to learn about their development process and how it maps to ISO 26262.
> If Tesla makes a "major" change to software, pretty much all bets are off as to whether the new software will be better or worse in practice unless a safety critical assurance methodology (e.g., ISO 26262) has been used. (In fact, one can argue that any change invalidates previous test data, but that is a fine point beyond what I want to cover here.) Tesla says they're making a dramatic switch to radar as a primary sensor with this version. That sounds like it could be a major change. It would be no surprise if this software version resets the clock to zero miles of experience in terms of software field reliability both for better and for worse.
I am admittedly a broken record on this point, but Tesla moves very fast and very nimble on a system that is under design controls. It would be very educational to learn about their development process and how it maps to ISO 26262.