←back to thread

171 points _sbl_ | 1 comments | | HN request time: 0.412s | source
Show context
threatofrain ◴[] No.44522729[source]
Bad engineering or impossible constraints?
replies(5): >>44522773 #>>44522774 #>>44522841 #>>44522892 #>>44523113 #
rsynnott ◴[] No.44522892[source]
Potentially both. If there are impossible constraints, then at a certain point you do _not_ build the impossible bridge, you say no instead.
replies(2): >>44522995 #>>44522996 #
spacemadness ◴[] No.44522995[source]
I am at a loss with all of the “well they were forced into it” comments. Don’t build it.
replies(2): >>44523088 #>>44523154 #
darth_avocado ◴[] No.44523154[source]
Have you never worked on projects where the management wants to do things a certain way but you know it’s just plain wrong. The only option sometimes is to let the slow rolling disaster unfold or risk your own job. Obviously this only applies where you aren’t risking people’s lives, but there is an entire subreddit dedicated for this. (r/maliciouscompliance)
replies(3): >>44523196 #>>44523215 #>>44524037 #
spacemadness ◴[] No.44524037[source]
You answered this yourself. We’re not talking consumer products. We’re talking civil engineering for bridges. You also can’t just ship medical device software with no basic testing that could injure people in the software world. If someone asked me to ship regardless I’d get it in writing and ensure my objections were clearly stated and also in writing.
replies(1): >>44525573 #
1. darth_avocado ◴[] No.44525573[source]
But you’d still ship… and that’s my point.

Also, depending on the org, you may or may not come out unscathed on the other side.