How to Make Your Automation a Better Team Player
summary
Argues that automation changes the whole socio‑technical system and often causes automation surprise—examples include Argo CD irreversibly deleting a site and multiple CI/CD misconfigurations that scaled services to zero; Terraform hides operation ordering and quota limits; opaque Kafka clients and unattended upgrades break operators. Recommends running automation as full services with status pages, logs, drill‑down of exact commands, explicit resource estimates and the ability to abort, and to build amplifiers not prostheses while always showing intended actions.
AI-written summary · about
chapters (8)
- 0:00Automation and teamwork intro
- 4:40Automation changes systems
- 10:41Automation surprises causes
- 17:49Preventing surprises in tools
- 22:49Avoiding bad recommendations
- 28:12Amplifiers vs prostheses
- 33:23Better automation design
- 34:06Summary
related talks
32mInfrastructure Automation (anti) patterns
15mAutomation Strategies: Real-World Experiences from F5 and
53mAutomation Automation Automation
32mSuriving the robot apocalypse: How technical writers can (and should) embrace automation
13mThe Automation Firehose Be Strategic and Tactical
47mWhat are your Automation Strategies?
04mAutomate!
48mAutomate and You Shall Conquer