Scripting and Automation: This Manual Task Could Have Been a Script
summary
Argues that small scripts can save hours but also spawn more automation and maintenance, showing concrete examples: The Decorator IDE plugin that grew into tests, CI and a CI + GitHub Action and worked well; a dirty Python script that converted file formats and later reused with five-line changes; and an automation that reduced a two‑day quarterly release to a one-liner release enabling continuous delivery. Warns of bugs-at-scale, tooling fatigue, maintenance cost and rigidity, and recommends documenting the process, automating incrementally and timeboxing attempts.
AI-written summary · about
chapters (8)
- 0:00Automation and scripting intro
- 2:21Automation in static analysis
- 4:49When automation is worth it
- 8:27Benefits beyond time savings
- 21:15Hidden automation costs
- 34:30Key factors for automation
- 47:09Practical automation approaches
- 52:55Q&A
related talks
53mAutomation Automation Automation
04mAutomate!
57mRise of the Machines - Automate Your Development
24mA Comedy of Errors
35mHow to Make Your Automation a Better Team Player
51mRedefining test automation
17mWe can automate that!
32mSuriving the robot apocalypse: How technical writers can (and should) embrace automation