So if I’m understanding this correctly. If anyone ever rolls out a software update that causes a failure like this it is instantly a sign that the company has a culture that leads to problems. Hard and fast? No exceptions? No one makes a huge mistake, that’s just a mistake that slipped through the cracks?
As for it being connected to the CAN bus, so what? It isn’t some sort of magical system where if something fails all the rest of the connected systems do too. That’s like saying if the monitor on my computer fails and it’s connected to the rest of my computer via the PCIe lanes on my graphics card, then everything else is going to be affected. It doesn’t work like that.
I don’t even have an opinion on the company I just don’t think it’s the end of times because the wrong build rolled out. They fucked up, they owned up to it and based on the response they will learn from it.
The issue is not just that a bad update went out. Freak accidents can happen. Software is complicated and you can never be 100% sure. The problem is the specifics. A fat finger should never be able to push a bad update to a system in customers’ hands, forget a system easily capable of killing people in a multitude of ways. I’m not quite as critical as the above commentor but this is a serious issue that should raise major questions about their culture and procedures.
This isn’t just some website where a fat finger at worst means the site is down for a while (assuming you do the bare minimum and back up your db). This is a vehicle. That’s what they meant about the CAN bus - not that that’s really a concern when the infotainment system just gets bricked, but that they have such lax procedures around software that touches a safety-critical system.
Having systems in place to ensure only tested, known good builds are pushed is pretty damn basic safety practice. Swiss cheese model. If they can’t even handle the basics, what other bad practices do they have?
Again, not that I think this is necessarily as bad as the other person - perhaps this is the only mistake they’ve made in their safety procedures and otherwise they’re industry leaders - we don’t know that yet. But this is extremely concerning and until proven otherwise should be investigated and treated as a very serious safety violation. Safety first.
If I have offended you, that wasn’t my intent. You seem defensive about what I said but I wasn’t trying to upset you.
I said broken monitors don’t necessarily affect the rest of the system. Just like, you know, broken infotainment systems don’t necessarily affect the rest of the car. Can happen sometimes, doesn’t seem to have happened this time. So yes what you are implying is that magic is happening when it clearly didn’t and to sit here and say it will definitely affect other systems misleading.
People make mistakes, it’s unavoidable but the fact that they are willing to admit it was their fault, shows an attitude of learning and growth and is a welcome change from norm, where companies sweep it under the rug and it costs people lives.
Will they probably grow to a point where they are too big to give a shit, probably. At least for now they are being open and honest instead of blaming the user or a third party.
We don’t live in a vacuum, the world isn’t black and white. Come live in the grey and cut people some slack.
So if I’m understanding this correctly. If anyone ever rolls out a software update that causes a failure like this it is instantly a sign that the company has a culture that leads to problems. Hard and fast? No exceptions? No one makes a huge mistake, that’s just a mistake that slipped through the cracks?
As for it being connected to the CAN bus, so what? It isn’t some sort of magical system where if something fails all the rest of the connected systems do too. That’s like saying if the monitor on my computer fails and it’s connected to the rest of my computer via the PCIe lanes on my graphics card, then everything else is going to be affected. It doesn’t work like that.
I don’t even have an opinion on the company I just don’t think it’s the end of times because the wrong build rolled out. They fucked up, they owned up to it and based on the response they will learn from it.
The issue is not just that a bad update went out. Freak accidents can happen. Software is complicated and you can never be 100% sure. The problem is the specifics. A fat finger should never be able to push a bad update to a system in customers’ hands, forget a system easily capable of killing people in a multitude of ways. I’m not quite as critical as the above commentor but this is a serious issue that should raise major questions about their culture and procedures.
This isn’t just some website where a fat finger at worst means the site is down for a while (assuming you do the bare minimum and back up your db). This is a vehicle. That’s what they meant about the CAN bus - not that that’s really a concern when the infotainment system just gets bricked, but that they have such lax procedures around software that touches a safety-critical system.
Having systems in place to ensure only tested, known good builds are pushed is pretty damn basic safety practice. Swiss cheese model. If they can’t even handle the basics, what other bad practices do they have?
Again, not that I think this is necessarily as bad as the other person - perhaps this is the only mistake they’ve made in their safety procedures and otherwise they’re industry leaders - we don’t know that yet. But this is extremely concerning and until proven otherwise should be investigated and treated as a very serious safety violation. Safety first.
Thank you for this response. I can agree with this perspective.
My comments were, “hey, let’s be a little more level headed about this” and less “this company should die and heads should roll”.
Interconnected hardware and software systems do affect each other. It’s not magic, it’s physics.
And yes, your graphics card spewing garbage onto the pci bus can affect the rest of your system.
It actually does work like that.
If I have offended you, that wasn’t my intent. You seem defensive about what I said but I wasn’t trying to upset you.
I said broken monitors don’t necessarily affect the rest of the system. Just like, you know, broken infotainment systems don’t necessarily affect the rest of the car. Can happen sometimes, doesn’t seem to have happened this time. So yes what you are implying is that magic is happening when it clearly didn’t and to sit here and say it will definitely affect other systems misleading.
People make mistakes, it’s unavoidable but the fact that they are willing to admit it was their fault, shows an attitude of learning and growth and is a welcome change from norm, where companies sweep it under the rug and it costs people lives.
Will they probably grow to a point where they are too big to give a shit, probably. At least for now they are being open and honest instead of blaming the user or a third party.
We don’t live in a vacuum, the world isn’t black and white. Come live in the grey and cut people some slack.