I like the checklist nature of this. I approached this problem from another side, which involved a very powerful REPL, but lacked the structure this shows: https://orestis.gr/clojure-unlocking-incremental-automation/
Do-nothing scripting: the key to gradual automation
91–100 of 126 posts
Re: Do-nothing scripting: the key to gradual automation
#92Is anyone else bothered by how they were handling ssh keys in the example? The whole point of public keys is that the private key never has to leave the box it’s generated on. Once you go sharing them you might as well just use a random passphrase.
As a user, I wouldn’t trust any private key that I didn’t personally generate.
If an IT guy sent me “here’s your new private key”, even through 1Password, I’d say “no thanks.”
Re: Do-nothing scripting: the key to gradual automation
#93Re: Do-nothing scripting: the key to gradual automation
#94We use this at my place, though in bash, and we call it executable documentation. Stuff like: NAME="$1" # Create directory for the code mkdir "$NAME" # Checkout the source cd $NAME && git something # and so on Sometimes with an echo "You need to read and understand this before just using it"; exit 1 thrown in somewhere for good measure. These files will have no logic, and make very little use of variables. They will…
This sounds like basically what I use READMEs or supplementary Markdown documentation files for, just in a bash code block in a Markdown file rather than in a bash file.
Re: Do-nothing scripting: the key to gradual automation
#95We use this at my place, though in bash, and we call it executable documentation. Stuff like: NAME="$1" # Create directory for the code mkdir "$NAME" # Checkout the source cd $NAME && git something # and so on Sometimes with an echo "You need to read and understand this before just using it"; exit 1 thrown in somewhere for good measure. These files will have no logic, and make very little use of variables. They will…
You could prefix the script with `#!/bin/bash -vn` and make it executable. It will just print itself.
Re: Do-nothing scripting: the key to gradual automation
#96This is a good idea. I recently wrote down some ideas about "How to Grow a Program," in a symbolic programming environment: https://github.com/theronic/hoist/
I call it Hoist - from "hoisting up" concrete, hard-coded values into abstract symbols for reuse. It's complete vaporware at this point, just a place to collect my thoughts for a future essay.
Re: Do-nothing scripting: the key to gradual automation
#97We use this at my place, though in bash, and we call it executable documentation. Stuff like: NAME="$1" # Create directory for the code mkdir "$NAME" # Checkout the source cd $NAME && git something # and so on Sometimes with an echo "You need to read and understand this before just using it"; exit 1 thrown in somewhere for good measure. These files will have no logic, and make very little use of variables. They will…
This sounds like basically what I use READMEs or supplementary Markdown documentation files for, just in a bash code block in a Markdown file rather than in a bash file.
The difference is that every time you do the process, you can consider writing a couple of tests and automating the step.
Re: Do-nothing scripting: the key to gradual automation
#98Interesting idea! I'll wrote some boilerplate that I think is a bit nicer:
https://gist.github.com/mbarkhau/60fc4bbe505914369ebd2fec1ab...
Re: Do-nothing scripting: the key to gradual automation
#99Why do I think that writing a script in Expect (https://en.wikipedia.org/wiki/Expect) would take as long as doing this and then you would be done?
Re: Do-nothing scripting: the key to gradual automation
#100Earlier quoted context omitted.
maybe he was a Java programmer? all joking aside, the reason he's doing classes seems to be an intention towards making a FooStep (and/or a BarStep) which could then maybe handle generic Foo stuff (authentication comes to mind) in the future?
"maybe"..."in the future" is the root of much object oriented evil
"maybe in the future" are four words I've learned to dread hearing from any developer. YAGNI goes much, much deeper than most people realize.