Recap and Practice
Key takeaways
- The command line is just a text box that does exactly what you tell it — words instead of clicks. An AI works by typing the same commands you would.
- The tells you where you are every time; most confusion comes from not knowing your current folder.
pwd,ls, andcdare 80% of what you'll ever do. rmis permanent — no Trash, no undo. Slow down onrm,sudo, and anything piping a download into your (curl ... | bash).- A dev server keeps running and looks "stuck" on purpose — that's it working. Ctrl-C stops any running program and gives you your prompt back.
- Read before you run. You don't need every flag, just a rough sense of the verb. When in doubt, ask the AI "what does this command do, and is it safe?"
Try it
Open your and explore without changing anything: run pwd to see where you are, ls to see what's there, cd into a folder and ls again, then cd .. to climb back out. Notice how the prompt updates each time. Now run a command that fails on purpose — type lss (a typo) and read the command not found message. You've just practiced the two safest, most-used commands and learned to read an error, all without touching a single file.
Prompt of the chapter
I'm a beginner on the command line and a bit nervous about running things.
Here's a command you (or a tutorial) gave me to run:
<paste the command>
- Explain in plain English what this command does, step by step.
- Tell me clearly whether it's safe, or whether it could delete files,
change my system, or run code with full permissions.
- If it's risky, suggest a safer way to do the same thing, or what to
check first.
- Tell me what folder I should be in before I run it.