Descriptor

Today I've watched a presentation by Marcin Stożek called  How to train your BASH  and wanted to remember the most interesting points for later. 1. It's best if you follow a style guide There seems to be only one though  Google Shell Style Guide . 2. You can set Bash to  "strict mode"   It sets more human-friendly defaults and makes sure you won't miss any errors in your scripts. #!/bin/bash set -euo pipefail IFS=$'\n\t' 3. Shellcheck Turns out there is a tool called  shellcheck  that can help you write scripts that you intended to write. Best thing is that it explains what's wrong and gives you suggestions on how you can fix it. 4. You can enable 'debug mode' when running your script Just pass " -x " to the script eg.  >  bash -x ./my_script.sh 5. Use Pure Bash No one wants to see weird errors when running the script on a new server so it's best if you avoid using external programs in your

This tweet made me remember my own pondering of the exact same question and how hard it is to guess what is going to be relevant in the future. A lot of people answer that by saying that you have to always learn but the question is not "Should I learn?" but "What I should learn?". Unfortunately, no one can predict the future. I would even say that the question itself is flawed. I'm reading Farnam Street blog for some time already and one of the last posts goes deeper into this problem: What’s Staying the Same ? If you start looking for things that are likely to stay the same you will find a lot of things that are worth learning and they should be relevant a lot longer than the newest fad. More to read: Lindy effect Algorithms to Live By