4 ms·
This feels like the “Documentation just goes out of date so don’t bother argument” Documentation (which is what a playbook is) isn’t milk, it doesn’t just “go
by simonbarker87 5y ago
This feels like the
“Documentation just goes out of date so don’t bother argument”
Documentation (which is what a playbook is) isn’t milk, it doesn’t just “go out of date”.
People let it go out of date by not keeping it up to date. Docs going out of date isn’t the problem, the problem lies in the system that causes it to go out of date.
The only reason automation doesn’t go out of date is because it breaks and so you have to fix it, the problem is that each of those little fixes takes time, probably more time that updating the docs.
Automation is great but to approach it as a binary choice is wrong.
- pydry 5y agoI was saying that the benefits of automating are often misaccounted for. In the examples above a 5 minute manual task run once a week, for instance, wasnt just a cost of 5 mins x 1 week. Automating potentially saved debugging time, time spent analyzing why the playbook went wrong, etc. Those benefits wouldnt typically be measured but theyre very real.