Very true! And once you've done it for a while, you start to notice other cachers by the way they are awkwardly standing in unusual places trying to look inconspicuous.
I, too, share your hatred for horses. They are arrogant fucks who think they are better then everyone else.
One exception: there's these large horses with fluffy hooves and fat asses that seem to be chill and more like large dogs. You're OK.
Nope. Shell scripts reside in Git repos on Gitlab/Gitea/Forgejo and are checked out using Ansible playbooks onto the servers as necessary.
For scripts? Python. Read this blog post by the great @isotopp@chaos.social. For interactive use? bash is just fine for me, though I've customized it using Starship and created some aliases to have colored/pretty output where possible.
Use shellcheck before running your scripts in production, err on the side of caution, set -o pipefail. There are best practices guides for Bash, use those and you'll probably be fine.
Be prepared to shave yaks. Take breaks, touch grass, pet a dog. Use set -x inside your Bash script or bash -x scriptname on the CLI for debugging. Remember that you can always fallback to interactive CLI to test/prepare commands before you put them into your script. Think before you type. Test. Optimize only what needs optimization. Use long options for readability. And remember: Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows your address.
Nope, it's absolutely not bad practice to create aliases to save you some typing in interactive shell. You shouldn't use them inside your scripts though, because they might/will not be available in other environments.
I switched to fish because it has tab completion
Yeah, so does Bash, just install it.
Oh, I also "curate" a list of Linux tools that I like, that are more modern alternatives to "traditional" Linux tools or that provide information I would otherwise not easily get. I'll post i
My wife has gained roughly 60 kg since I meet her many years ago, which some might see as that kind of limitation, but you know, I don't even see that when I look at her. She is smart as fuck, a great engineer, a wonderful mother, and just overall the better half of me. It's just so easy to love her, and I would never even consider leaving her for looks. We all have our imperfections, but that's not to say we're not worthy of love.
Oh yeah, I'm a terrible smart ass, overweight, impatient, not a great father, and I don't communicate very well. Beats me what she sees in me.
Not exactly what you're looking for, but for an understanding of the general directory structure in Linux, you might want to have a look at the Filesystem Hierarchy Standard (FHS 3.0). It defines which directories need to exist and what they are supposed to contain. Also, it's a rather light read and not awfully technical.
If you want more of a deeper dive, you might want to get a book that can be used in preparation for an LPIC-1-certification, even if you never intend to take the actual test. I found that they do a really good job at teaching not just the user perspective of Linux (type this to do that), but also the reasoning behind why Linux works the way it does.
The dog was the best!