Lessons Learned in Automation
summary
Covers concrete, repeatable practices: how to log every automation event and measure resource‑hours saved so business impact is reportable, when to aim for a minimum viable product decomposition instead of overengineering, and which engineering habits actually matter (PowerShell cmdlets, source control, unit tests, CI/CD). Draws on career‑long case studies—what got built, what failed, and what approvals or cost savings followed—plus practical advice for dealing with org constraints at SMB, commercial, and enterprise scale.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 7:12Automation matters to business
- 10:23Automation pitfalls and solutions
- 15:22Planning automation projects
- 20:39PowerShell automation basics
- 26:18Structuring automation clearly
- 32:12Communicating automation value
- 36:23Advanced automation improvements
- 38:49Q&A
related talks
38mAutomation Is Hard & We Are Doing It Wrong
48mAutomate and You Shall Conquer
55mThe Troubles of Automating “all the Things”
38mWhy Automating Everything Adds to Your Toil
21mThe Essential Pillars of Automation Testing for Success
58mPrinciples of Network Automation
47mWhat are your Automation Strategies?
32mWhat Not to Automate