/Command Line

What Helps People Get Comfortable On The Command Line?

- Julia Evans tl;dr: Various strategies and resources to help people become more comfortable with using the command line. It identifies three main areas to focus on: reducing risks, finding motivation, and utilizing resources. To reduce risks, the article suggests regular backups, using tools, avoiding wildcards, and building --dry-run options into scripts. Motivations might include finding a "killer command line app" or being inspired by command line wizardry. Resources include utilizing tools like explainshell, fzf, and oh-my-zsh, and seeking help from experienced friends or co-workers. Cheat sheets, aliases, and workshops are also mentioned as helpful aids.

featured in #440

CLI Tricks Every Developer Should Know

- Kedasha Kerr tl;dr: “We’ve compiled some important tricks and commands that every developer should know from GitHub’s own engineers. By mastering these basic techniques, developers can become more efficient at working with the command line and gain a deeper understanding of how the underlying operating system and programs work.”

featured in #410

Commandlinefu

tl;dr: “The place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.”

featured in #399

Best Practices For Inclusive CLIs

- Rohan Kumar tl;dr: "This began as a reply to another article that lists practices to improve user-experience of command-line interfaces... Unfortunately, a number of its suggestions are problematic, particularly from an accessibility perspective." Rohan elaborates on these and and discusses best practices for inclusive CLIs. 

featured in #325

UX Patterns For CLI Tools

- Lucas Costa tl;dr: "Most technical people choose GUIs not because GUIs are the best tool for the job. People choose GUIs because the CLI alternatives usually suck. That’s my hunch. In this blog post, I’ll cover good UX patterns for CLI applications. Furthermore, when applicable, I’ll compare how these UX patterns help developers replicate the valuable characteristics of most good GUIs."

featured in #324

A List Of New(ish) Command Line Tools

- Julia Evans tl;dr: "My favourites of these that I use already are entr, ripgrep, git-delta, httpie, plocate, and jq." Julia breaks this list into replacements for standard tools, new inventions, and less-new tools. 

featured in #308

GitHub CLI 2.0 Includes Extensions!

- Billy Griffin tl;dr: "Creating extensions is simple. Each extension is just a repository prefixed with gh-, and you can easily define the extension. We even built tooling into GitHub CLI itself to allow you to get started more quickly with gh extension create, which creates a scaffolded repository for you with some pre-written Bash that will help you get started."

featured in #248

6 Command Line Tools For Productive Programmers

- Adam Gordon Bell tl;dr: (1) Broot is a "better version" of tree (2) Funky “takes shell functions to the next level by making them easier to define, more flexible, and more interactive.” (3) FZF is a command-line fuzzy finder, and more.

featured in #244

Command Line Interface Guidelines

- Aanand Prasad Ben Firshman Carl Tashian Eva Parish tl;dr: "An open-source guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day."

featured in #218

HTTPie

- Jakub Roztocil tl;dr: "A user-friendly command-line HTTP client for the API era. It comes with JSON support, syntax highlighting, persistent sessions, wget-like downloads, plugins, and more."

featured in #190