Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Does this mean that we can't write software for drones anymore?

What about software for missile guidance? Is that okay by this oath?

Or do we as a community value not texting people at 6AM more than we value not killing people?



Strawman. And anyway plenty of software developers (and other engineers) won't work on armaments.


So should a software developer's code include armaments, or not?

If it does, it would never get mainstream acceptance; if it doesn't, but does cover the topic of this post, it will be ethically absurd.

I don't see how this is a straw man; when building a professional code, one has to choose what actions to allow or disallow, and this seems like a topic that would obviously come up. What do you think about this scenario misrepresents the idea of a developer's professional code?


This is an internal debate I've had with myself since reading Bernard William's Objections to Utilitarianism [0].

I've never had to actually face the ethical dilemma of developing weapons, but what if the development improved precision on a missile? If we can ignore the question as to whether a missile is ethical or not, developing a better guidance system for a missile will help limit collateral damage, but could increase the "comfort-level" of using the weapon for those who decide such things, therefore increasing overall death/destruction. Utilitarianism is hard, because taking all factors into account is impossible. Kind of like machine learning.

I will never scoff at someone who turns down work for ethical objections, but some people are more pragmatic than others.

Both of Williams examples are really hard to wrap your head around if you accept the situations as presented. They are similar to a Sophies Choice [1]

[0]: http://plato.stanford.edu/entries/williams-bernard/#Day [1]: http://en.wikipedia.org/wiki/Sophie%27s_Choice_(novel)


This is a divergence, but it seems to ignore the value that comes from propagating the meme that building armament systems is unethical by refusing to participate in it.


While the idea of an oath may be flawed, I do think it's about time some segments of the tech field showed a little less contempt towards users. I don't know how that would happen, but launching your own startup shouldn't give you carte blanche to exploit your users however you see fit.

As a programmer, I don't want a bunch of charlatans in SF to give my career an unsavoury reputation because of these antics.


That's a decision for each individual developer to make.

Some folk tried to create a pacifist version of the GPL[1].

Others are using the RMPL (RobotGroup-Multiplo-Pacifist-License)[2] - basically a MIT license, but with a restriction that bans military projects.

[1] http://arstechnica.com/uncategorized/2006/08/7511/

[2] http://multiplo.com.ar/soft/Mbq/Minibloq.Lic.v1.0.en.pdf


The irony being that the government isn't strictly bound by copyright or licensing terms. They can and have violated them as needed.


> That's a decision for each individual developer to make.

I generally agree with this, which is why I find the idea of a "developer's code" somewhat ridiculous.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: