This is true, but when safety is on the line it actually goes further than that. As an engineer you have an ethical duty to say no to making a product unsafe for end users or the general public.
It doesn’t matter if you get fired, if your boss goes to the media to bitch about you, if your boss threatens to sue you, you as an engineer hold a position of public trust to keep the people that use your product safe. If you don’t respect that and take it seriously, well we see where oceangate ended up.
Yeah my boss has been going back and forth with me on this for months. Wanting to release unsecured products to the general public. I’m getting exhausted with him. I hold the keys and frequently I’ve told him no, and threatened to quit. Each time they just retreat back and hold a meeting how it will “stay on dev for now”. The features aren’t even feasible to release in the near future but I know they will force the issue. My resignation letter is on the table.
The number of times I’ve rejected something because of security flaws (usually database injection), only to see other engineers later approve and merge the pull request is infuriating. There seems to always be an engineer who is willing to make an unsafe product.
Yep, it’s a damn shame, but we’re gonna let them do that because we don’t want to be responsible for deaths or security flaws and ultimately there’s organizations and people out there who value that if our current jobs don’t
This is true, but when safety is on the line it actually goes further than that. As an engineer you have an ethical duty to say no to making a product unsafe for end users or the general public.
It doesn’t matter if you get fired, if your boss goes to the media to bitch about you, if your boss threatens to sue you, you as an engineer hold a position of public trust to keep the people that use your product safe. If you don’t respect that and take it seriously, well we see where oceangate ended up.
Yeah my boss has been going back and forth with me on this for months. Wanting to release unsecured products to the general public. I’m getting exhausted with him. I hold the keys and frequently I’ve told him no, and threatened to quit. Each time they just retreat back and hold a meeting how it will “stay on dev for now”. The features aren’t even feasible to release in the near future but I know they will force the issue. My resignation letter is on the table.
I’ve been there, my boss once interrupted me to ask me to turn our product into a quadcopter
“Sir, with all due respect, I don’t believe turning a commercial diesel filling station into a quad copter doesn’t seem feasible.”
It tracks with the zoomers. Make it happen.
You just need to think outside the box. like these lads did: https://youtu.be/ReAa2WFm8Vc?t=16
This is the most management-ass thing I’ve heard in a while!
The number of times I’ve rejected something because of security flaws (usually database injection), only to see other engineers later approve and merge the pull request is infuriating. There seems to always be an engineer who is willing to make an unsafe product.
Yep, it’s a damn shame, but we’re gonna let them do that because we don’t want to be responsible for deaths or security flaws and ultimately there’s organizations and people out there who value that if our current jobs don’t
That value is instilled in many types of engineering, but not as much in software engineering.
And the people paying the engineers are highly motivated to keep it that way