[bermanoid]

We shouldn't make as stable constructions as other engineers, for very good reasons: they're building things out of concrete, iron, and steel that are meant to last for years doing a very predictable job without alteration after their initial construction. If you don't get it 100% right before you close up a building, it's going to cost millions to go back and fix it.

As programmers, conversely, we build text files that are expected to change every day as the business needs shift, and we know up front that most of the code that we write will not survive as-is. Speed of iteration is far more important than getting things right the first time, and the cost of a delay in the name of building something right can be much higher than the cost of refactoring the simplest solution that can possibly work once you actually need to (YAGNI is not something you'll hear very often in physical engineering fields).

[tropo]

The other engineers do their part, and then software controls it. Bad software destroys things. People get killed by accident.

Then there are the security holes in things that will never get updates, the malware-infested webcams and TVs... this too impacts the world.

We can combine it all: connected cars. This isn't "other engineers". It's software developers -- call them programmers or software engineers if you like.

[stale2002]

Sure. In the very rare situation of connected cars, or infrastructure, it is important that code quality is bullet proof.

Fortunately most developers write web and mobile apps.

It doesn't really matter that much if 1% of the time the add friend button doesn't work on the Opera web browser.