Needless to say, he returned to our company as a consultant on some project that had incurred budgetary overruns and incompetency.
All at the hands of our so-called American trained "engineers."
I can't speak to the specifics of this situation but I have seen others where the desires of in-house personnel were ignored but when the same initiatives are suggested by a consultant, they're followed with gusto.
Don't blame the engineers, blame the management.
I get it. That's a part of why I typically try to negotiate non-standard start times when I take a position. Starting work at 09:30 makes for a much more relaxed commute both to and from work.
If/When telecommuting become the norm, most of my problems will be behind me because I'll be able to live and work far enough outside of the city that none of their decisions will have any impact upon me.
I had a cousin and her family come to town from Maryland and when it was time for them to go home, I tried to give them directions to the Turnpike. It was literally take the next four right turns and then drive about 6 miles, you'll see the signs.
She was like Nope, I'm GPSing it. The GPS gives her valid directions but they were longer and more complicated.
I was amused but she got home safely.
Whomever performed the modification, if that modification is the cause of the incident.
It's not like we're discovering new issues here.
In 1968, if you took your Buick to your neighborhood fix-it guy and he used sub-standard wheel bearings and they caused the wheel to fall off and kill someone, Mr. Fix-it would be liable.
Really, this isn't rocket science just because the story includes the word "firmware".
Make sure your code does nothing gracefully.