>_

How the Terminal Works

beginner

The text interface behind every developer tool.

Terminals look ancient because they are — and they've outlived every 'replacement' because text commands compose, automate, and travel over SSH like nothing else. This track explains the machinery: what a shell actually is, how commands are found and run, where the text goes, and why your terminal understands colors. Pairs with the Bash track, which teaches the commands themselves.

DevelopmentServers & SSHAutomationDebuggingEvery Dev Tool Ever
0%
0/7 lessons

Setup

You already have one. This track explains what it is — the Bash track covers commands in depth.

Bash
# Windows Terminal (get it from the Microsoft Store)
# runs three different shells:
#   PowerShell  — Windows-native (see PowerShell track)
#   cmd.exe     — the 1980s legacy shell
#   WSL bash    — a real Linux environment

wsl --install     # recommended for this track's examples

Lessons

1
Terminal vs Shell — Two Different Programs
People say 'the terminal' for the whole experience, but it's two programs: the t
2
What Happens When You Press Enter
'ls -l' — Enter — output appears. Between those two moments: parsing, an environ
3
stdin, stdout & Pipes
Every program is born holding three data streams: input, output, errors. Redirec
4
Environment Variables & Shell Startup
Why does PATH exist in every window? What is .bashrc actually for? Environment v
5
Colors, Cursors & Full-Screen Apps
Terminals only move bytes — so how does text turn green? How does vim own the wh
6
SSH — Your Terminal, Any Machine
The payoff for all this text-protocol archaeology: because a terminal session is
7
Terminal Cheatsheet
The mental model plus the keystrokes, on one page.