Every time I "fuck up", I add a few commands to a shell script, so I don't mess up the next time. Over time that has grown into over 1000 lines of shell, e.g.

Every time I "fuck up", I add a few commands to a shell script, so I don't mess up the next time. Over time that has grown into over 1000 lines of shell, e.g. https://github.com/oilshell/oil/blob/master/devtools/release.sh https://github.com/oilshell/oil/blob/master/devtools/release... And this is why I'm writing a shell -- because it's good for automating things that you are otherwise too lazy to automate! I find that "semi-automation" is a good middle ground. This is where shell is better than "real" languages. You don't have to commit to writing a polished program -- you just incrementally improve things and it makes problems go away. The time you put in is saved immediately, as opposed to other languages, where you might spent 30 minutes writing something that will save you 2 minutes in the next year, which isn't necessarily worth it. If you keep a text file with a bunch of terminal commands, then you might as well chmod +x it and put #!/bin/sh on the front. That's what a shell script is! ---- Here is the output of the release process, which has tarballs, change logs, documentation, test results, benchmarks, etc. https://www.oilshell.org/release/0.7.pre5/ https://www.oilshell.org/release/0.7.pre5/ It's way to much to do by hand.