Sometimes this is true, relative to the purpose at hand. Take a mediocre web developer and ask them to build a smarthome system, and you end up with a wire protocol of raw, unverified, unfiltered Python code in plain trxt, running under eval() on a grossly underpowered microcontroller (true story, was fixed eventually AFAIK, not naming names).

There's something to be said for the discipline that comes from working in a resource-constrained hardware/software project. We could benefit from more cross-pollination between industries, as long as experienced engineers are sanity checking the resulting ideas (Python is not a protocol!).

If a go kart manufacturer made a kart whose roll over cage failed in any circumstance we would not excuse it by saying that there is more money to test in the automotive side of the industry.