Course contentModule 1 · Lesson 2
Module 1 · Lesson 2
The Terminal, Without Fear
You open the terminal for the first time, move around inside it, and create your first project folder without touching a single line of code.
MODULE 1 / THE TERMINAL
The terminal has a reputation, and it is the wrong one. A black window, a blinking cursor, cryptic characters: that looks like a hacker movie, and that image alone keeps a lot of people from ever opening it. Let's set the record straight. The terminal is not a myth and not a test of your intelligence. It is a completely ordinary way to talk to your computer, just with words instead of mouse clicks.
In this lesson you open it, move around inside it, and create a folder for your projects. Nothing more. By the end, you will wonder what you were ever nervous about.
What the terminal is, and what a shell does
When you double-click a folder, you are telling your computer with the mouse: "show me what is in here." The terminal does the same thing, except you type the instruction. The window you type into is the terminal. The program that reads your typed line and carries it out is the shell. You type an instruction, press Enter, the shell runs it and shows you the result. That is the whole trick.
Why type at all, when clicking exists? Because a lot of the tools for working with AI agents live in the terminal, and because typing is precise. A click is hard to explain, a command is not. That is exactly why we work this way here: so you can name and understand every step.
Opening the terminal
How you open the terminal depends on your system (you noted yours down in Lesson 1):
- macOS: there is an app called Terminal. BuilderBob shows you where to find it and how to open it.
- Windows: in this course we work through WSL, the Linux environment inside your Windows. The terminal you open for it behaves like a Linux terminal. BuilderBob sets up WSL with you and shows you how to open it.
- Linux: you already have a terminal program on board; BuilderBob helps you find it.
I am deliberately keeping the exact click path short here, because menus and names change with system versions. The mental model stays the same: you are looking for the app that gives you a window with an input line. That is your terminal.
The handful of commands you actually need
You do not need to learn a hundred commands. To get started, four questions you can ask your computer are enough. I will give you the concept behind each; the exact command for your system comes from BuilderBob, and it explains each one before you type it.
- Where am I right now? The terminal is always at a specific place in your file system, inside a specific folder. There is a command that tells you this current location. That is your anchor: whenever you are unsure, ask first where you are.
- What is in here? A command lists what sits in the current folder: files and subfolders. That way you can see whether you are in the right place, and whether something you just created is really there.
- Where do I move to? A command moves you from one folder into another, the same way a double-click takes you into a folder. That is how you navigate through your file system.
- Create a folder. A command creates a new, empty folder at your current location. That is how you build your project folder in a moment.
Four questions: where am I, what is in here, where do I go, create me a folder. With these four, you move around with confidence.
You are still working completely without an account, and that stays true for this whole lesson. You do not need to sign up for anything to use the terminal. Only from Lesson 3, when the real setup begins, do you create a free account and carry your progress with you.
Copy-paste hygiene: the most important habit
Here is the one rule you should take away from this lesson, more important than any single command:
Never run a command you cannot explain.
Online you will find ready-made commands to copy everywhere. Some are harmless, some are not, and you cannot tell the difference just by looking at a copied command. So on your workbench, this rule holds: before a command lands on your machine, you know what it does. BuilderBob works with you the same way. It explains every command before you type it, and if you do not understand something, you ask instead of blindly pressing Enter. This one habit protects you through this whole course, and well beyond it.
VS Code as a gentle bridge
There is an editor called VS Code that many people use to work. The useful part: it has a terminal built in, right inside the familiar program environment. It is the same terminal, the same shell, the same commands, just inside a window that looks a little less bare. If the plain black window feels foreign to you at first, the integrated terminal in VS Code can be a gentle bridge.
Just do not mistake the bridge for the destination. The target of this course stays the plain terminal, because that is what lets you find your way around anywhere, no matter which environment you end up in. VS Code is the comfortable entry point, the terminal is the skill that stays with you.
Check yourself
You are done here once you have done this with your own hands:
- You moved around inside the terminal: you know where you are, you displayed what sits there, and you moved into another folder.
- You created a project folder and moved into it.
That is a small step and a big one at the same time. You worked with words instead of clicks for the first time, and you created something of your own on your machine. That is your first small win on the workbench.
From Lesson 3 it gets concrete: installing tools, understanding what happens along the way. For that, create your free account now, so your progress stays saved and the path keeps guiding you step by step. Lessons 1 and 2 were the free preview. From here, watching turns into doing.
Knowledge Check