How Not To Build Your CLI’s
summary
Lists the anti-patterns that cause data loss and automation failure with concrete examples: git branch -D and Docker’s capital -P missteps, curl’s -d / -X surprises, and a joke about a 500MB clock CLI. Explains POSIX and GNU flag rules, recommends concrete fixes like --delete --force plus confirmation, use of --method/-m, YAML firewall configs, dry-run and --no-interaction for scripting, clear help and error messages, semantic versioning, and smaller binaries for predictable, automatable CLIs.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:14Every flag a landmine
- 2:00Ambiguity and verbosity
- 3:23Avoid config and automation
- 4:06Interactivity and mystery flags
- 5:08Bloat and unhelpful errors
- 5:52Conclusion
- 6:12What is POSIX
- 8:40Apply POSIX standards
- 10:06Clearer flags and commands
- 11:51Config files and dry runs
- 12:34Subcommands and automation
- 13:19Footprint and versioning
- 14:23Helpful help and errors
- 15:28Open for questions
related talks
37mCLI's Aren't As Easy As You Might Think
37mLet's Make Better Command Line Applications
16mBuilding an interactive CLI app in Elixir
26mBuilding Great CLI Experiences in Node
56mDevOps: How to train your Bash
25mReinventing the CLI with Go
27mHow to Write a Great Command Line Application
36mCLI applications & TDD: Never write scripts again