Orientation: the chapter ahead

1. The promise

You'll know what this chapter teaches, why every chapter after it needs the terminal, which terminal application you'll run on your own machine by the end, and what is not covered here (Git, Node, npm — those come later).

2. The mental model

The terminal is a steering wheel.

Up to now you've been a passenger using a touchscreen dashboard. The file manager, the icons, the right-click menus — all good for what they do, all built around your finger or your mouse. After this chapter you're driving. The hand position feels awkward for a week and then it doesn't.

(DIAGRAM: Block 1 chapter map — flowchart — Ch 0 → Ch 1 → Ch 2 (highlighted) → Ch 3, with a one-line summary on each)

This is the most uncomfortable chapter in Block 1 and the most rewarding. Typing instead of clicking will feel slow for a few days. Then it will feel faster. Then the file manager will feel slow.

3. You do it, with me

There's nothing to install in this unit. Read along.

The vocabulary you'll meet in this chapter. Each of these is a new word. Each one gets defined inline the first time it shows up in a later unit. You don't need to memorise them now. You're just being told they're coming.

• shell, terminal, prompt — the three things people confuse (Ch 2.1).
• command, argument, flag — the parts of one line you type (Ch 2.3, 2.6).
• pipe, redirection — sending output from one command into another, or into a file (Ch 2.8).
• glob, wildcard — patterns that match many filenames at once (Ch 2.9).
• env var, PATH — the shell's memory, and the one variable that decides if node works (Ch 2.10, 2.11).
• alias, profile script — your own nicknames and the file the shell reads on startup (Ch 2.12, 2.13).

Both sides, every time. This chapter doesn't pick a side. Every unit with terminal commands shows two columns: bash/zsh (the shells you run on macOS and Linux) and PowerShell (the shell you run on Windows). You learn the one you have, and you can read the other.

(SCREENSHOT: macOS Terminal.app on first launch — full window — prompt cursor visible)

(SCREENSHOT: Windows Terminal on first launch — full window — PowerShell tab open, prompt cursor visible)

What success looks like by Ch 2.14. You can open a terminal, walk to a new project folder, build a folder structure, create files, edit a config file, and read a log — without opening the file manager once. That's the deliverable.

What this chapter does not teach.

• Git. Comes in Ch 8. The terminal is the place you'll run Git from, but Git itself isn't installed here.
• Node and npm. Come in Ch 14. You'll install a version manager first, in Ch 8.
• Homebrew or winget. Mentioned in passing in Ch 2.2; used properly from Ch 8 onward.

Setting expectations now protects you from scope creep later. If you've read elsewhere that you need Git "right away", that source was wrong for the path you're on.

The honest minute estimates. The chapter is short on paper — under four hours of reading. In practice it takes longer, because typing slowly is part of the work. Don't speed-read. Type every command.

(SCREENSHOT: chapter index page for Ch 2 — full window — unit 2.0 highlighted in the sidebar)

The assignment at the end. Ch 2.assign is a shell-only file-management exercise. You build a small project folder tree using only the terminal. No file manager. About 75 minutes. The gate to Ch 3.

4. What you should be seeing

A clear picture of three things in your head:

1. What's covered. Moving around, creating, copying, deleting, reading, piping, wildcards, env vars, PATH, shell config, aliases.
2. What's not covered. Git, Node, npm, package managers.
3. What the deliverable is. A terminal you can live in, and a one-page list of twenty commands you know by heart.

If you can list those three things without looking back, you're done with this unit.

5. Common stumbles

• You open the chapter, see a black window with white text, and assume something's missing. Nothing is missing. That's what a terminal looks like. No icons, no toolbar, one blinking cursor.
• You try to install Git or Node "to get ahead". Don't. The next time you'll touch those is Ch 8. Installing them now means installing them twice, in two different ways, and undoing the first install.
• You worry you should already know all the vocabulary. You shouldn't. Every word gets defined inline the first time it appears in a later unit.

6. You should know