I'm a fan of --safety-off. It gives off a 'aim away from face' or 'mishandle me and I'll blow a chunk out of your DB' vibe.

Totally agree it shouldn't be for basic tools; but if I'm ever developing a script that performs any kind of logic before reaching out to a DB or vendor API and modifies 100k user records, creating a flag to just verify the sanity of the logic is a necessity.

    if [ -n "$DRY_RUN" ] ; then
        alias rm='echo rm'
        alias cp='echo cp'
    fi

Of course, output redirects will still overwrite the files, since the shell does it and IIRC this behaviour can't be changed.

set -o noclobber

Yep. First thing I do for this kind thing is make a preview=true flag so I don’t accidentally run destructive actions.

Now I like that idea as an environment variable that takes precedence over the command parameters.

Please just let me believe I can double my lifespan as percieved by the rest of the world by becoming the average founder.

I've been hosting a Teamspeak server for more than half my life, it's acted as the communication hub for the majority of my time gaming.

It's fallen off in terms of features and UX. But I feel the warm and fuzzies knowing that my memes and conversation aren't being fed into some neural network owned by microsoft.

I also love that I can just change the voice codec to whatever I please without me or my users forking over a monthly fee.