Command-line usability: A terminal user’s thought process
I’ve been thinking about the usability of command-line terminals a lot recently. Command-line interfaces remain mystifying to many people. Usability hobbyists seem as inclined to ask why the terminal exists, as how to optimise it. I’ve also had it suggested to me that the discipline of User Experience (UX) has little to offer the Command- […]
I’ve been thinking about the usability of command-line terminals a lot recently. Command-line interfaces remain mystifying to many people. Usability hobbyists seem as inclined to ask why the terminal exists , as how to optimise it. I’ve also had it suggested to me that the discipline of User Experience (UX) has little to offer the Command-Line Interface (CLI), because the habits of terminal users are too inherent or instinctive to be defined and optimised by usability experts. As an experienced terminal user with a keen interest in usability, I disagree that usability has little to offer the C
saved by
related reading
- Command Line Interface Guidelinesclig.dev
- CLI Style Guide | Heroku Dev Centerdevcenter.heroku.com
- GitHub - jlevy/the-art-of-command-line: Master the command line, in one pagegithub.com
- Learning From Terminals to Design the Future of User Interfaces — brandur.orgbrandur.org
- GitHub - jlevy/the-art-of-command-line: Master the command line, in one pagegithub.com
- GitHub - jlevy/the-art-of-command-line at jlevy-patch-1github.com
- How I Use Claude Code | Philipp Spiessspiess.dev
- The terminal is on life support. Is it worth saving? | Warpwarp.dev
- Command K Barsmaggieappleton.com
- 10 Usability Heuristics for User Interface Design - NN/Gnngroup.com
- UI/UX Design Inspiration & User Flows from Top Apps — Page Flowspageflows.com
- An AI OS from a design perspectivenewsletter.f2n.co