Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I write some software to automate some engineering processes in construction.

I'd say it comes from some of (order of most to least imo, but I'm only mid level so take what I say accordingly):

* physical processes have a fuzzy good enough. The bridge stands with thrice its expected max load. It is good enough.

* most software doesn't have life safety behind it. In construction, life safety systems receive orders of magnitude more scrutiny.

* physical projects don't have more than 20 different interdependencies; there's an upper limit on arbitrary complexity

* physical projects usually have clearish deadlines (they lie, but by a constant factor)

* The industries are old enough that they check juniors before they give them big decisions.

* Similarly, there exists PE accountability in construction



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: