Evil Tech: How Devs Became Villains
summary
Shows a clear claim: engineers face structural ethical tradeoffs, not just bad intent. Cites the code of ethics (1987) and a literature scan finding only 16% of SE papers discuss ethics, with security ranked highest then benevolence/universalism. Gives concrete tensions: building end‑to‑end encryption protects user privacy but enables criminal use and hinders moderation, and biased datasets break self‑driving models. Maps stakeholders (users, makers, affected third parties), notes legal pushes like the European Accessibility Act, and urges empathy‑based stakeholder analysis.
AI-written summary · about
chapters (13)
- 0:00Welcome
- 5:48Defining villains in tech
- 16:28Society’s values shape tech ethics
- 22:09Ethics in software engineering research
- 27:14Developers as ethical gatekeepers
- 31:49Q&A: Telegram arrest & data privacy
- 33:16Q&A: Content moderation & control
- 36:09Q&A: Security vs accessibility
- 38:39Q&A: AI bias & consequences
- 41:31Q&A: Future misuse of tech
- 44:01Q&A: Intent vs impact
- 45:51Q&A: Ethical career choices
- 49:03Closing
related talks
41mEvil Tech: How Devs Became Villains
47mThe Ethics of Software - some practical considerations
50mBeing an ethical software engineer
30mEvil Tech: How Devs Became Villains
37mEthics in Software Engineering - Should We Care
40mEthics in Computing
31mSoftware Ethics in a Software World: Where are we?
36mAn engineer's code of ethics