Evil Tech: How Devs Became Villains
summary
Starts with an audience evil laugh exercise and moves to concrete claims: a 1997 software engineering code of ethics exists but is too rigid, and only 16% of SE papers address ethics. Presents a simple stakeholder method — the ugly Gothic wedding cake — to list who is affected and their concrete concerns (end users worry about data sale and liberty; engineers worry about breaches). Highlights a measurable disconnect: privacy vs security are treated differently by users and developers, and recommends building empathy by routinely mapping stakeholder harms before shipping.
AI-written summary · about
chapters (6)
- 0:00Introduction and evil love
- 5:57Why developers are called villains
- 11:23Ethics and human values in tech
- 21:27Stakeholders and ethical concerns
- 31:12Empathy as the solution
- 38:43Ethical dilemmas at work
related talks
50mEvil Tech: How Devs Became Villains
47mThe Ethics of Software - some practical considerations
37mEthics in Software Engineering - Should We Care
01mthe ethics of software development needs to be discussed
31mSoftware Ethics in a Software World: Where are we?
50mBeing an ethical software engineer
40mEthics in Computing
49mThe Ethical Engineer