Unemployment is a different constraint, but still a very real one. Doesn't matter now principled you are, there's always someone who'll take the money that isn't. Maybe these seven were the scabs and the heroes who said "no" are just forgotten.
As a design engineer, all you can do is explain to the stakeholders how the constraints will affect the outcome and suggest alternatives.
Ultimately, the engineers will have to work with what they are given, and as long as the outcome is safe and its limitations are communicated, they can't be blamed.
The ones who plan ahead tend to not end up in these organizations to begin with since they have leeway to say no much earlier.
The job of an Engineer implies a capacity for technical judgment and willingness to not do something if it's unsafe or doesn't make sense. Even if we're not official, licensed "Professional Engineers," we still need to make these calls and stop projects like this from happening. Whether it's building a ridiculous, unsafe bridge, or building ridiculous, defective software, if the engineer doesn't have the agency to stop it, who does?
Just letting it happen and letting it fail with a "malicious compliance" smirk on our faces is passive aggressive, and doesn't elevate our profession.
The only way to make this kind of thing work is by threatening to send people to jail. Like building-engineers having to report asbestos, or electricians being forced to report code violations and authorities actually following up on it. Of course regulation is like kryptonite for the engineering/HN crowd, so let's keep building shit on thoughts and prayers.
You think the corrupt politicians didn’t know about the design of this bridge? It doesn’t take a genius engineer to see it’s fucked.
That engineering signoff is a rubber stamp on a corrupt project. Fire the politicians not the person who has to rubber stamp it (because again, they’ll find somebody to signoff on it… the signoff is a mere formality on a project like this)
i don't think that's necessarily the case. civil engineering implies personal responsibility. we get to pretend like our bad choices don't have real-world impacts because we don't have a universal standards board or mandated ethical guidelines for computer engineering (in the vast majority of cases).
Also, depending on the org, you may or may not come out unscathed on the other side.
Again, if I’m being asked to risk people’s lives, I’d push back harder and resign if I can’t change minds, but I’m not doing any of that to “elevate our profession”.
But we all know the reality of whether we expect moral pushback from the armed forces for just about anything.
Was it a good deal when hundreds of thousands of bystanders died in Iraq? It doesn't matter. It's not the place of the rank and file to question authority, regardless of constitution this or moral that. The same is true for rank and file engineers.
As long as software engineers can be fired for denying to do things asked by people in power, "standards" and "ethics" take second place. This applies to virtually every profession, so maybe start making bad bosses and bad managers take actual responsibility for their irresponsibility before blaming on engineers.
In life there is no responsibility when there is no autonomy. And as much as certain crowds love to say "just walk way", giving away your means of survival is also not real autonomy. This is not WW2.