Question 1

Bash vs Zsh — which should I learn?

Accepted Answer

Bash: 30+ years, universal (ships on every Unix/Linux/Mac), POSIX-compatible, scripts run everywhere. Zsh: modern, interactive features (completion, history), friendly syntax. Learn Bash first for portability and career breadth — it's the standard for deployment scripts and cron jobs. Zsh after, for your personal shell. Write production scripts in Bash, interactive shell in Zsh. Zsh on macOS is now default, but servers still run Bash.

Question 2

When should I use Python instead of shell scripts?

Accepted Answer

Use shell for: file operations, tool orchestration, simple data pipelines, deployment steps, cron jobs, quick 10-50 line tasks. Use Python for: complex logic, data structures, unit testing, maintenance >1000 lines, portability across OS (Windows, macOS, Linux), dependency management. Rule: if your script needs classes, error handling beyond `set -e`, or complex iteration, switch to Python. If it's gluing tools together, stay in shell.

Question 3

How do I handle errors properly in shell scripts?

Accepted Answer

Start every script with `set -euo pipefail`: -e stops on error, -u errors on undefined vars, -o pipefail fails if any pipe stage fails. Use functions with explicit return codes. Trap errors: `trap 'echo Error at line $LINENO' ERR`. Quote all variables: `"$var"` not `$var`. Test edge cases: empty input, special characters, large files. Use ShellCheck (`shellcheck script.sh`) to catch common mistakes before runtime.

Question 4

What does ShellCheck do and why should I use it?

Accepted Answer

ShellCheck is a linter that finds bugs and portability issues before runtime. It catches: unquoted vars, unreachable code, deprecated syntax, inefficient patterns. Run on every script: `shellcheck myscript.sh`. Integrates with editors (VSCode ShellCheck extension). Warnings = code smell, errors = bugs. Passing ShellCheck is non-negotiable for production scripts. Disable warnings sparingly (`# shellcheck disable=SC2086`) only when you understand the risk.

Question 5

How do dotfiles work and should I version control them?

Accepted Answer

Dotfiles (.bashrc, .zshrc, .config/) are shell config and environment setup. Version control them in a git repo (with a README explaining symlinks or bootstrap script). Symlink into home: `ln -s ~/dotfiles/.bashrc ~/.bashrc`. Benefits: reproducible environment, share across machines, collaborate with team. Never hardcode secrets (use .env or `pass` password manager). Popular pattern: `~/dotfiles/install.sh` creates symlinks, runs once per machine.

Question 6

What are common pitfalls and how do I avoid them?

Accepted Answer

Pitfall 1: Not quoting variables — causes word splitting and globbing. Fix: `"$var"` always. Pitfall 2: Using `ls` in scripts — parsing output fails with spaces. Fix: use glob patterns or `find`. Pitfall 3: Parsing JSON/YAML with regex — fragile. Fix: use `jq` (JSON) or `yq` (YAML). Pitfall 4: Hardcoding paths — breaks on different systems. Fix: use `$HOME`, `readlink -f`, or relative paths. Pitfall 5: No error context — hard to debug. Fix: add logging and use `PS4` for trace output.

Question 7

How do I make my shell scripts portable across systems?

Accepted Answer

Write POSIX-compliant code, not Bash-only. Use `#!/bin/sh` not `#!/bin/bash` when possible. Avoid: `[[]]` (use `[]`), `=~` regex (use `grep`), arrays (use loops). Check syntax: `sh -n script.sh`. Test on multiple systems (Mac, Linux, BSD). Use `env bash` in shebang if Bash required. Document dependencies (jq, curl, awk version). Use `command -v` to check if tools exist before using. Ship with `install.sh` that checks requirements.

Region	Junior	Mid	Senior
USA	$85k	$115k	$160k
UK	£52k	£70k	£98k
EU	€58k	€78k	€110k
CANADA	C$88k	C$120k	C$168k

Shell Scripting

What is Shell Scripting

📋 Before you start

💰 Salary by region

🎓 Certifications

🎯 Careers using Shell Scripting

⚖ Compare with

❓ FAQ

Not sure this skill is for you?

Find your ideal career path