The result is that these engineering disciplines have practices that are much more rigorous. If you think about it, a recall is essentially a hardware patch, and they are typically highly embarrassing and costly.
There is also the whole separate aspect of professional licensure which certain engineers get. Licensed engineers are expected to hold their work to certain standards regardless of the business needs of the company they work for. Now i'm not saying what Tesla did falls in this category, but it certainly looks like designing a product below the standard expected for that product. (what most people would call shoddy engineering).
In software we often get away with this, because we can put in the work later on, and also because people often have insanely low expectations of how well software will work.
I feel like this is the self fulfilling prophecy. We definitely didn’t use to ship software we knew would break, because we literally shipped it on disks, and delivering updates was hard.
The internet has been good for many many things. Software reliability hasn’t been one of them.
An argument can be made for both. Malfeasance in that it was a significant and potentially catastrophic engineering tradeoff due to unknown failure modes, and arrogant in that the decision valued company vision over potential consumer safety risks as well as over the expertise of the component manufacturers.