Earlier this week, a post written by programmer and teacher Bill Sourour went viral. It's called "Code I'm Still Ashamed Of."
In it he recounts a horrible story of being a young programmer who landed a job building a website for a pharmaceutical company. The whole post is worth a read, but the upshot is he was duped into helping the company skirt drug advertising laws in order to persuade young women to take a particular drug.
He later found out the drug was known to worsen depression and at least one young woman committed suicide while taking it. He found out his sister was taking the drug and warned her off it.
By sake of comparison, take a look at the ACM Code of Ethics and Professional Conduct (Adopted by ACM Council 10/16/92.)
(Score: 4, Insightful) by Immerman on Tuesday November 22 2016, @10:20PM
If they enabled something they didn't expect, certainly. On the other hand if you build someone a weapon knowing how they plan to abuse it, then you carry a share of the responsibility of that abuse. Similarly if you create a tool that you know can be easily abused for great gain - human nature being what it is the existence of that tool nearly guarantees it's abuse, and you bear a responsibility for bringing it into the world, even if you're confident that those who will initially control it have no intention of doing so.
And before you think I'm arguing we should stop advancement for fear of what *might* happen, I'm not. But if your creation gets twisted into something evil then it's right and proper that you should feel guilty about the monster you helped create. *Especially* if you saw that potential before you created it.