Otherwise, they’ll find out how loyalty is rewarded nowadays.
Otherwise, they’ll find out how loyalty is rewarded nowadays.
This is why we need very strong whistleblower protections.
Which is not really my point as to why they should be held responsible. The reason is the real world consequences of their actions and the scale and ease of introducing negative consequences by tech creators.
However, the "yeah, sure I can add in a GPS locator module" and the "yeah, I can add analytics that reports when the train is in a maintenance hanger" and the "the catastrophic program halt code module used in cases of extreme failure is located here, but why do you want to know that?" all seem less than unethical.
Theoretically you only need one unethical line of code, so how it got there, I think, is pretty important to know before passing ultimate judgement.
EDIT:
Of course for something like train control software, you really should have a process or at the very least responsible engineers that would notice a middle manager with limited technical skills asking suspicious questions and then pushing up a PR that is self approved.
I would be more than willing to entertain an ethical debate along those lines. Although, like I said, I think it's important to understand the whole story because the specifics really do make a difference.
Whoever implemented this, if you read this, you are a very bad person and destructive for society.
If you want this to not happen, you need to incentivize refusing to do this more than the existing incentive to do this.
Otherwise, punishment only changes who's in the chair next time.
(Future possible punishment is not a very good disincentive, which is why increased prison sentences don't deter crime.)
(not expecting this, but would be nice)