I don't know any serious business that embraces 'breaking things' when a bit more effort and time ensures that nothing gets broken.
This is more understandable in software which is more disposable, but the same concept can still apply in other industries. It applies more in the research phase before development of the actual product.
Really, the only branch of industry where this kind of attitude makes sense is infotainment. Everywhere else - when there is money by paying customers on the line - it is as good as handing your customers to the competition.
Software is hard, and firmware is harder. Every modern car has computers to handle a number of very important systems (ignition, diagnostics, ABS, traction control, throttle, speed plate, and so on). Break-fix cycles are almost unavoidable in today's world. It happens with lowly kitchen appliances, and it happens with cars, trucks, airplanes, boats...
It's the normalization of failure that's the problem here.
R&D that is not willing to break things will stagnate.
Then you're out of touch. The whole 'move fast and break things' refers to production.
Breaking things only makes sense when the stuff you built is small enough to not matter much (it's a tradeoff, etc)