3 ms·
I've read (and probably written) many a playbook that has dated badly. In many cases having the playbook was worse than no playbook at all because it drove me
by pydry 5y ago
I've read (and probably written) many a playbook that has dated badly.
In many cases having the playbook was worse than no playbook at all because it drove me down some blind alleys ("oh yeah we stopped using that acccount for X months ago..."). You can often not be certain if it's you who did something wrong or a bug in the playbook, especially if some elements are vague.
In other cases I've written a playbook, somebody else has read it and missed step 4 and we've together spent many hours tracking down the issue in a playbook that ought to take 5 minutes to go through if run consistently. And conversely ive done the same thing - we are all. fallible.
I think even for tasks that are run infrequently code automation can be more cost effective because it can avoid the above scenarios by being executed consistently and failing noisily and obviously.
- Zababa 5y agoOn the other hand, in my team we have playbooks and they're great. One thing that helps is to consider them as living documents (we have a tool with history and comments that helps, Quip), use them every time you do the task instead of relying on memory, and put a comment every time you encounter a problem so that the playbook can be improved. To give a bit of context, this is for tasks usually done once a week to once a month individually, multiple times a week for the whole team.
- simonbarker87 5y agoThis 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.