shell-scripting

Error handling in bash requires `set -euo pipefail` at the script start to enable fail-fast behavior: exit on errors, treat undefined variables as fatal, and propagate pipe failures. Combine this with explicit error paths, input validation, and defensive checks before file operations to catch issues early and prevent silent failures.

POSIX compliance ensures scripts run across bash, zsh, and other POSIX shells on any Unix-like system. Avoid shell-specific syntax, use portable argument parsing patterns, prefer POSIX builtins over GNU extensions, and document language-specific features. This maximizes compatibility without rewriting for each environment.

Secure shell scripting requires defensive input validation, quoting all variable expansions, avoiding eval, using explicit file permissions, and sanitizing command arguments. Apply secure defaults like umask settings, validate user input before processing, and use explicit error paths to prevent unintended command execution or file access.

Robust argument parsing uses getopt or getopts patterns with explicit handling for flags, options with values, and positional arguments. Validate all inputs before use, provide clear error messages for invalid options, and document expected arguments. This makes scripts maintainable and prevents silent argument misinterpretation.

Shell scripts excel at system automation, file operations, and Unix tool orchestration without external dependencies. Use them for quick automation, deployment tasks, and tools that combine existing commands. However, for complex logic, data processing, or cross-platform GUIs, compiled or interpreted languages often provide better maintainability and performance.

Debug shell scripts using `set -x` for command tracing, adding debug output before risky operations, and testing argument parsing separately. Combine defensive input validation with explicit error messages that identify failure points. Use shellcheck linting to catch common mistakes before runtime.