Which ethics (if any) are relevant to programming?

Question

Does ethics have anything to do with programming? Let's think analogously about a doctor. Does a doctor's job have anything to do with ethics? Well, I suppose even a sociopath can get the degree and perform their residency, but it is crucial that doctors do think about ethics. They need to know whether its OK to perform abortion, euthanasia, cloning, stem cell research, etc. - apart from the legality in any particular state, and apart from the technical aspects!

Similarly in computer science, ethics are important. We have questions on here (stack overflow) whether to implement features on a system that will inevitably be used for spying. What about spamming?

So it seems to me that there are ethical questions that are relevant to programming. If so, what are they? Conversely, what are the irrelevant ethics? (And "all ethical questions are irrelevant") is a fine answer (though I would think incorrect), just defend the assertion.

Answer 1

The ACM code of ethics is the standard.

http://www.acm.org/about/code-of-ethics

You guys can add your own ethics after this. :)

Answer 2

The ACM (Association for Computing Machinery) has a Code of Ethics that I think is very well thought out: http://www.acm.org/about/code-of-ethics

Also, check out this post: http://stackoverflow.com/questions/86708/what-should-be-included-in-a-programmers-code-of-ethics

Answer 3

"Dont be evil" - Thats that best ethical guidline I have come across in software.

Answer 4

Even though the question is a directly to computer science.

Being a computer engineer, IEEE code of ethics could be look into.

Answer 5

Ethics are more about the person and the social group (society, peers, etc.) than the field of work. If your ethics tell you spamming is unethical, don't contribute to it. If your ethics apply only to your job they're probably too arbitrary to be ethics at all.

Answer 6

The analogies to medical science don't end there. "First, do no harm" is applicable for both doctors and programmers, IMO.

Answer 7

Frankly, I don't think you can list it all. Perhaps some of it can be classified.

You can find youself in situations where you are directed (or just tempted) to write code that breaks the law.

• Example: I've often refused to use someone else's code in violation of their licensing agreement.

You can find yourself in situations where you are directed or tempted to "cut corners" on testing or proper software design in situations where human safety is an issue.

• Example: I once refused to interview with a company that coded firmware for medical devices in C (about the most error-prone language in existence).

You can find yourself in situations where the actual intended purpose of the code you are directed to write violates your morals.

• Example: I once turned down a job offer writing firmware for smartbombs. I know someone's gotta do it, but it ain't gonna be me.

You can find yourself in situations where you are directed to write code that isn't inherently immoral, but is inherently flawed, or indirectly encourages bad behavior.

• Example: This is a bit squishier, but I've been dragged kicking and screaming into doing jobs that implemented dongles and license servers. Coding a voting machine with no paper trail would be another good example.

The thing you have to realise about most of these issues is that your bosses don't have your perspective as an expert in software, so often they don't even realise they are asking you to do something unethical. It isn't a comfortable thing to have to do, but if you don't point it out, the evil one is really you, not them.