I get it, but this script looks a lot like a checklist to me. Seems like a checklist is a good place to start, no?
If you want more "interest" during the process, make it a point to refine the documentation for your process (clarify a step here, split one command into two steps). Then you have a very clear spec by the time the process needs to be automated.
I think the value of using a script as your checklist is that the script can handle some of the book-keeping for you, including making it harder to lose track of where you are.
Each part of a script can be replaced with actual code over time without committing to trying to automate the entire thing. I think itβs a pretty nifty idea that helps avoid putting the whole thing off for later.
If you want more "interest" during the process, make it a point to refine the documentation for your process (clarify a step here, split one command into two steps). Then you have a very clear spec by the time the process needs to be automated.