Slashdot Mirror
Why Engineers Must Consider the Ethical Implications of Their Work
An anonymous reader writes "An article by Abbas El-Zein at The Guardian explores the ethical responsibilities for engineers who create and maintain 'technologies of violence.' He says, 'Engineers who see themselves as builders of the shelter and infrastructure for human needs also use their expertise in order to destroy and kill more efficiently. When doctors or nurses use their knowledge of anatomy in order to torture or conduct medical experiments on helpless subjects, we are rightly outraged. Why doesn't society seem to apply the same standards to engineers? There is more than one answer to the question of course, but two points are especially pertinent: the common good we engineers see ourselves serving and our relationship to authority. ... Our ethics have become mostly technical: how to design properly, how to not cut corners, how to serve our clients well. We work hard to prevent failure of the systems we build, but only in relation to what these systems are meant to do, rather than the way they might actually be utilised, or whether they should have been built at all. We are not amoral, far from it; it's just that we have steered ourselves into a place where our morality has a smaller scope.'"
(posting AC due to content)
I worked on a military project in the early part of the 2000s focused on cracking cell-phone encryption technology. At the time, it was just an interesting problem, with the potential to maybe "help fight terrorism". I didn't really think a lot about the implications of the work, I was just glad to have an interesting job.
I've now got a bit more perspective. Maybe the technology I worked on helped us catch Osama bin Laden. Or maybe it's helping the NSA listen to American citizens. Maybe both.
I don't think it's as simple as saying that engineers are responsible for all of the uses of the technologies they build, but I don't think we can ignore all responsibility either. Something I think about a lot these days.
I was brought in to a government contractor's project as consultant during the Vietnam War. They were having severe problems with building their software system, and expected me to help them identify the root causes. For two weeks, they hemmed-and-hawed, trying to keep from telling me the true purpose of the system. Finally, when it was clear they couldn't understand the root problems themselves, they briefed me on what the system was ACTUALLY intended to accomplish. They did this on a Friday.
I was appalled that American citizens could dream up such an incredibly horrible intention: I can't say more, but the goal (in part) was to efficiently kill innocent civilians.
My choice was clear: I packed up, went to the airport, and bought a ticket home. On Monday, I was back at my regular desk. There was simply no way my conscience would allow me to optimize the schedule and effectiveness of such a project. There was never any repercussion, from anyone. I understand the contract was cancelled for non-performance several months later.
We who understand technology need to make value judgements: Do YOU want to write code that disadvantages fellow citizens? Do YOU want to create systems that transfer wealth from middle-class to rich folks? Do YOU want to write code that has secrets that could harm someone in the future buried inside? Do YOU want to make money by cheating ordinary citizens (think High-frequency "trading")? Do YOU want to see more systems, like NSA's, that violate the constitution, the law, and common decency?
I didn't, and I don't. Stand up for what you believe.