Arrested DevOps Live...
summary
Panel argues that ethics and concrete engineering choices matter: an IoT sensor is made product that can't identify individuals and becomes a competitive advantage; teams find open open S3 bucket mistakes and treat PII like toxic waste; machine‑learning models reproduce developer bias; HIPAA workflows show how much effort actually protects data. Calls for concrete actions — threat‑modeling, deleting unneeded fields, using GDPR teeth or hiring choices — and reports that speaking up and leaving bad employers sometimes changes outcomes.
AI-written summary · about
chapters (15)
- 0:00Welcome
- 0:43Conference curation
- 3:32Ethics keynote
- 6:02Software culture
- 7:26Data privacy
- 10:41Abuse-resistant design
- 13:10Data breaches analogy
- 15:37ML biases in lakes
- 17:00Data purpose and control
- 18:24Tech neutrality ethics
- 20:11Technologists speaking out
- 21:56Security priorities
- 22:59Breach cost externalization
- 24:04Legislation role
- 26:14Actions for technologists
related talks
42mInfosec, AI and ethics – new models for a secure future
29mArrested Devops LIVE!
27mBalancing Innovation with Responsibility Ethics in Cloud Native Development
30mOrganizing for your Ethical Principles
44mAn Engineer’s Code of Ethics
25mThe Ethics of the Internet of Things
24mThe Social Responsibility of Coding
32mDigital Ethics in an Unethical Era