One of the leads and myself are the only people who call out the fact that we are humans and we will make mistakes. And on a 24/7 operation that means production issues will happen.
The other lead insists we all act like robots and he gets frustrated when people don’t like his proposals.
Edit: Just saw that the driver was an "amateur car racer", which exponentially increases the chances that he re-flashed his ECU.
Personally I don't like trusting safety systems entirely to software, but I could see it being a decision a big corporation makes to simplify manufacturing (cut costs).
This could be misleading. From the small article at least, the only action I assume that was done was the cruise control being disengaged from it's faulty state. There is no evidence that a rogue service employee could play real life mario kart from afar (although it wouldn't surprise me).
I also somewhat expected this from a high end car manufacturer in this day and age. Why is this inherently a bad thing? Surely it would do more good than bad, would it not?
What bothers me is the poor response time.
inb4 privacy concerns, big brother, etc. I'm thinking engine shutdowns during car chases (expensive vehicles are a target), etc.
I assume every software engineer under the age of ~50 would have learned about events like the Therac-25 incidents during their education. Is there genuinely no robust software quality regime in place for critical systems like this in vehicles?
There are so many worrying things here: such a bad failure occurring in the first place; the lack of any physical fallback or failsafe; the ability of the dealer to remotely control the car's operation (!!) – any of these by themselves fills me with dread.