Taming Code Quality in the Worst Language I Know: Bash
summary
Bash is full of real hazards but can be tamed by concrete practices: enable set -eu -o pipefail to avoid silent failures, run shellcheck for hundreds of common pitfalls, and use the bash-support plugin plus IntelliJ formatter for consistent style. Watch for undefined-variable rm -rf disasters, CRLF line endings, quoting/globbing and array gotchas. Applied in a large banking project, these rules and integration tests (Dockerized) keep long-lived production scripts working.
AI-written summary · about
chapters (8)
- 0:00Start
- 16:05Summary of the Bash Weaknesses
- 22:05Google Style Guide
- 28:47Shell Strict Mode
- 35:22Whitespace Formatting
- 42:58Final Thoughts
- 43:58Questions
- 45:05Where Would You Draw the Line between Using Close of a Scripting Language Bosh and Higher-Level Scripting Language Python
related talks
23mBash and All That; Why Ancient *NIX Tools Are Still Essential
21mFrom Scratch to Shell: Building Your Own Functional Bash
52mLinux terminal for java developers — boost your efficiency!
01h 01mThe Linux Shell - From Novice to Wizard
32mImplementing and Validating Linux Cyber Security Requirements: SEAPATH, a Case Study
29mBash shell scripts for Windows & Linux development with Qt
02mSafe Systems with Linux MC Wrap up and next steps
01h 10mEnhancing Spatial Safety: Better Array-bounds Checking in C (and Linux)