Most of the places I've ended up working used tcsh (holdovers from Unix days). Both interactively and a large pile of small scripts. A few of us who were willin

Most of the places I've ended up working used tcsh (holdovers from Unix days). Both interactively and a large pile of small scripts. A few of us who were willing to troubleshoot ourselves would use Bash, Fish, or another shell interactively. None of the libraries were set up for Bash/sh so it was difficult to write scripts that weren't for personal use. It was an April Fool's joke that we were moving to Bash and I was bummed. I spent some personal time making our libraries agnostic (a bulk of the code was Python, but environment stuff shelled out or inherited from the tcsh scripts). I think it's worth focusing on Bash, but at least contrasting it with csh and pointing out the lineage and other options. Perhaps spending some time writing some scripts in sh since there is a large install base of outdated or missing Bash. I have no idea what schools think about this. I generally prefer deep knowledge in a single language, but there is value in learning a bunch of languages so picking up yet another new language is trivial. When I've spent too much time in one specific language I've found it harder to switch around.