Command Cheat Sheet

While Graphical User Interfaces (GUIs) are intuitive for exploration, the Command-Line Interface (CLI) remains the industry standard for software engineering and DevOps.

CLIs are highly automatable, scriptable, and operate with minimal system overhead. They form the backbone of modern CI/CD pipelines where no human is present to click a button.

Every standard CLI program communicates using three data streams:

• stdin (Standard Input): Data piped into the program (e.g., from your keyboard or another command).
• stdout (Standard Output): The normal results printed by the program.
• stderr (Standard Error): A separate channel used strictly for error messages and diagnostics, so they don't corrupt the actual output data stream.

The true power of CLI tools comes from the Unix philosophy: "Write programs that do one thing and do it well."

By using the pipe operator (|), you can string together multiple simple commands to perform incredibly complex tasks. For example, cat logs.txt | grep "ERROR" | wc -l instantly reads a massive file, filters for "ERROR", and counts the resulting lines, all in memory without needing a dedicated log analysis app.