zlacker

>>belter+(OP)
Every time I read about space engineering, I'm amazed by how contingencies have contingencies. It's so much careful planning and rigor compared to my world. I can always re-compile, re-deploy and regularly realize that my job is not life or death.

>>notyou+Bc1
Honestly, I'd say most engineering is like that outside of the software world. In the classic engineering disciplines with actual licensures at the end of the pipeline, the responsibility and ethics of this are ingrained into students from day 1. (Budget and importance of the application doesn't always allow for the indulgence of this though, at least to a point.)

This type of thinking also follows from decades of experience.

For some reason the software engineering world largely abandoned esteem and respect for all of the above.

>>Engine+pg1
It’s not the licensing or the ethics classes or the responsible thinking or the professors that causes some engineering disciplines to be more carful.

It’s the cost when something fucks up.

If I’m holding my phone near a cliff, and I rely on it for navigation and I’m hours from civilization, I’m a little more careful, not because I’m normally super careful. It’s because — in that specific scenario — losing my phone would cost me so much and the chance of it happening is much more likely.

Space companies spend a little extra because the cost is years of development and billions of dollar evaporating in a few seconds.

And there are software teams in certain industries that dot their I’s and cross their T’s as well.

Even on some dumb CRUD app, if it’s a critical piece of code that the rest of the software hinges upon, you spend a little extra time because the cost of fuck up is so major.

Or you’re launching a product and you have a sign up that will seed your user base, you damn well make sure it works.