Exploring the Unintended Consequences of Automation in Software
summary
Research extracts automation mentions from The VOID: 10,000+ public incident reports, narrows 459 keyword hits to just under 200 manually reviewed, and uses thematic coding to classify six roles automation plays. Findings: automation is a contributing factor most often, 87% had multiple automation roles; humans must intervene ~34% of the time; automation helps only ~25% of the time and hinders remediation ~14%. Recommends designing for joint cognitive systems and directable, negotiable agents rather than blind substitution.
AI-written summary · about
chapters (6)
- 0:00Intro
- 5:47Unexpected consequences of automation in software
- 17:23Research from The VOID
- 25:33Automation themes
- 27:32Better automation through joint cognitive systems
- 34:02Outro
related talks
31mExploring the Unintended Consequences of Automation in Software
05mA Case Against Automation
38mWhy Automating Everything Adds to Your Toil
32mWhat Not to Automate
38mAutomation Is Hard & We Are Doing It Wrong
42mWhen /bin/sh Attacks: Revisiting "Automate All the Things"
55mThe Troubles of Automating “all the Things”
13mBeyond the hype: What test automation really costs