Earlier quoted context omitted.
> because it was written by under-experienced software "engineers." I used to be an infotainment software engineer for an Auto maker. There’s this idea in the software industry that because the software behaves poorly on your car’s system, it must’ve been written poorly by someone who didn’t know what they were doing. In my experience it was almost always a matter of the hardware being stretched way past its limits.…
That still just sounds like people not knowing what they're doing. In no world would automakers say, "Hey you know, we just did all of this tire engineering with this rubber, but let's change the composition at the last minute and not retest all of its physical properties." So, why should it be any different with software? Because some sucker PM didn't have the brains to say, "We can't actually do that."?
But then the seats kick on automatically when the car starts and the driver tucks in with her morning coffee for a commute down the highway. The coffee kicks in, the cabin heats up, and suddenly that warm seat is like sitting on a griddle. She taps on the menu to bring up the seat controls, then lag, then has to hit the seat heat button twice to go from “high” to “low” to “off”, lagging each time. Oh, she hit it three times, now it’s on high again. Tap, tap, tap, tap… Meanwhile she has crossed three lanes of traffic and is staring down a jersey barrier at 70+ mph.