For four days I have handed you commands one at a time. Today I stop, because there are thousands of them and I am not a good way to learn thousands of anything. Almost every tool on your machine can describe itself. Once you know how to ask, the rest is yours.
Ask the tool, not the internet
ls --help
Prints what ls does and every option it takes.
The first line that comes back is the important one. On my machine it reads: Usage: ls [OPTION]... [FILE]... — that single line is the whole grammar of the command line, and we are about to read it properly.
Why this beats searchingThe help text comes from the exact version installed on your computer. A blog post might be four years old and describe a flag your version does not have. This cannot be out of date — it is the tool talking about itself.
Every command has the same three parts
ls -la Documents
Command, then flags, then the thing to act on.
ls is the command — the tool you are running.
-la are flags. They change how it runs, not what it runs on. Here: show the long detailed form, and include hidden files.
Documents is the argument — the thing you want it done to. Leave it out and the command uses wherever you are standing.
That shape almost never changes. Which means ls -la is no longer four characters to memorise — it is a sentence you can read, and take apart if it does something you did not expect.
One dash or two
One dash takes short flags, single letters, and lets you stack them. Two dashes take the full word. So -la is not one flag with two letters — it is two flags sitting together:
ls -l -a
Exactly the same as ls -la. I compared both outputs on this machine — identical.
ls --all
The long name for -a. Longer to type, easier to read in a saved script.
When --help gives you a wall of textSome tools print hundreds of lines. Two ways through it: pipe it into a search, which is Part 6 and worth waiting one day for, or run man ls, which opens the full manual page — press q to leave it. If man is not installed in your Git Bash on Windows, do not worry about it; --help always works.
The habit this replacesPasting a line from a search result that you cannot read. That is how people delete the wrong folder — not by being careless, but by running something they never understood. Read the flags first. It takes ten seconds.
Do this in 60 secondsRun ls --help and read only the first line. Then find -a in the list below it and read what it says. Then run ls -a where you are standing and see the hidden files appear. You just learned a flag without being taught it.
Today’s AI angleA coding agent does this constantly. Handed an unfamiliar tool, it runs the tool with --help and reads the output before deciding what to type. Later, in Part 11, you will see that an MCP server works the same way: it describes its own tools so the model can read them instead of being told. Self-description is the whole idea, at both ends of this course.
You can now read any single command. Next comes the idea that made the command line outlive every app built to replace it: what happens when you stop running commands one at a time and start joining them together.