5 ms·
I can't find it now but I remember reading a post on HN with the suggestion to make all your runbooks shell scripts, even if all they start out as a series of p
by PebblesRox 4y ago
I can't find it now but I remember reading a post on HN with the suggestion to make all your runbooks shell scripts, even if all they start out as a series of prompts walking the user through the checklist of manual tasks.
This way you can incrementally automate various pieces of it so that gradually the user is doing less and less, but there's continuity on their end: run the script and do whatever it says to do next.
- TheFlyingFish 4y agoI'm guessing this is "Do-nothing scripting: The key to gradual automation" https://news.ycombinator.com/item?id=29083367 https://news.ycombinator.com/item?id=29083367 Although the example uses Python, rather than shell.
- PebblesRox 4y agoThat’s it, thank you!
- dougsillars 4y agoI love this idea! The automate the easy bits (or the steps that are the biggest pain/time suck) until the whole thing is completed. A tool like Jupyter Notebooks would be great for this - comments & code can be placed into a single document. I'm working on a project called unSkript (https://unskript.com https://unskript.com) that is built on this idea.