If you're intimidated by code there's a good reason. Every heist movie has a hacker. And that hacker has a laptop with a black screen and green gibberish running down it.
And worst of all…
They must have some kind of superpower because there's no way a normal human can read that much, that fast.
Except, that black screen is where Claude Code lives... the AI tool non-developers are also using to get real work done. In the next ten minutes, I'll introduce you.
If you're like me, the first time you opened one of those black screens with the blinking cursor by accident you quickly closed it. You know, that wall of text could start deleting the pictures of your children or something.
Well, turns out it's not as scary as the movies make it out to be. And, yes, you can use one too.
Friends, let's put on our blank, grey hoodies and corded earbuds. It's time to learn about the command line terminal.
What's a terminal?
That wall of code is a different language. Which is why it's unknown and scary looking. But just like a child, you can learn to see patterns, then start understanding it, then reading, then writing simple sentences.
Before there were icons and menus and folders you can see on your screen, it was just text. You typed something and the computer would do it. Want to delete a folder? Instead of dragging and dropping in the recycle bin, you type a command (just words in a computer language) and the computer does it.
I always thought that when I dragged a file into the trash, the computer would just secretly do that command, but I was wrong.
If your computer is a house, clicking with your mouse and using the terminal are two different doors you can use to get inside and do things.
An Illustration: Pointing vs. Talking
Let me break it down in a different way. You're traveling in France, except you don't speak French. What do you do? You point to a croissant. Hold up two fingers. You shrug as if to say "how much?"
And the baker responds in respectable English.
I mean… you get by fine with pantomiming but you can't explain anything in depth.
Imagine you learned the language. You could say things like "also two almond scones from the back, but only if they are baked today (they are), and box up whatever's left at closing on Friday and I'll pick it up and pay double."
Pointing works on what's visible, one thing at a time. Language handles what you can't see (almond scones), only do this if that (baked today), and many at once (what's left at closing).
Now, In Terms of Terminal
You have 400 screenshots on your desktop. You're a little embarrassed when your coworker looks over your shoulder and asks you to show them something. Today you're cleaning it up.
Pointing: You COULD sort, scroll, select, drag each screenshot from your desktop into a folder you aptly named "Sort-Later." One thing at a time. aka: point at the croissant.
Talking: In the terminal, you say this:
mkdir Sort-Later mv *.png Sort-Later/
Here are two sentences. The first one makes the folder (mkdir = make directory). The second one moves the files. mv means move, Sort-Later/ is where they're going.
Then there's *.png. The * stands in for any characters at all, so in other words "everything in this folder ending in .png." Every screenshot on your desktop, in one go, whether there are nine of them or nine hundred.
Why use a Terminal?
There's power and precision in using the terminal which will come into play later when making AI do things for us. Let's put it simply for now.
Coders have never stopped using the terminal. Scale, repeatability, precision, and reusability is why. But here's why, in terms of croissants. Which is better.
Buy 1000 croissants at once (scale) every Friday (repeatability) and not one less (precision) from every bakery across France (language reusability), even if the bakeries have no doors or windows.
Let's break down that last one a minute.
This article you're reading right now lives on a computer in a warehouse somewhere. That computer has no screen, no mouse, no desktop to drag anything onto. Text (aka terminal commands) are the only way in and it's one of the most important reasons why the terminal never went away.
The one thing the movies got right
Remember the pictures of my children I don't want to delete? So there's one scary thing I don't want to shy away from.
Imagine that house with two doors — one for the terminal and one for the desktop and mouse. Except there's no trash can next to the terminal's door. You can't put on your yellow, latex gloves and sort through the banana peels to find the pictures of your kids because there's just a big, ol' furnace. No "are you sure?" If you tell it to delete something, it deletes it, and it doesn't announce what it did. The Trash can you're used to was invented later for the mouse.
So the habit you'll need is to look before you touch.
Ask to see the screenshots before you move them:
ls *.png
ls just lists. It just reads it, so it can't hurt anything. Does it show you what you expected? Then you can run the real command. Does it have your W-2 and your wedding photos? Then maybe not.
This is the exact same process we'll use later when deciding what AI can and can't do.
So where do I start?
Let's start right now, actually.
Open a terminal. On a Mac, hit Command + Space, type "terminal," press Enter. On Windows, hit the Windows key, type "powershell," press Enter.
There's the blinking cursor. Deep breath. Here are four commands. Since this is a blog you found on the internet, paste each of these in your AI (Claude, ChatGPT) and ask "what does this do in my terminal?" for practice. First, we say "where am I?"
pwd
"Print Working Directory." The terminal is always standing in one folder, and this tells you which one. I think this is the idea that helps with everything else. You're not hovering above your computer the way you are in Finder. Think about you standing somewhere inside it. Now, let's look around.
ls
"List." Same as opening a folder and looking, except you're looking to see what's inside the place in the computer where you are (from pwd).
cd Desktop
"Change Directory." This is like walking into a new room, in this case, your desktop. Now run ls again and you'll see your 400 screenshots (just kidding, your desktop is probably neat and tidy). Does that help it click that what you see is the same as in your desktop? Also see the path before the cursor? That's where you are. Now here's where being precise matters. Include the space and two periods exactly as they are below.
cd ..
This is like saying "go back up." Two dots means the folder above this one. That's it! Like walking around your computer.
Let's get a little fancy.
Press Tab. Start typing cd Desk and hit Tab. The terminal finishes the word for you. Do this constantly. It's faster, and it's safer too because it can only complete names that actually are on your computer (less typo mistakes).
Press Ctrl + C. Whatever's happening, that stops it and gives you your cursor back. This is like a kill switch to stop whatever's happening.
Your new tools
- pwdWhere am I?
- lsWhat's here?
- cd / cd ..Go in / come back
- TabLet it type for me
- Ctrl + CMake it stop
You now know how to walk around your own computer using words, and every scary-looking command you'll ever use is that plus a verb to tell it what to actually do.
So what does this have to do with AI?
Remember the house with two doors? Here's the thing I've been building up to: coding agents like Claude Code live in the terminal. When you open Claude Code, it opens inside a folder. And now you know exactly what that means, because you've stood in one. pwd tells you which room the AI is standing in. ls shows you what it can see from there. cd is how you walk it over to the project you actually want help with.
And that "look before you touch" habit? That wasn't just about protecting the pictures of your kids. It's the exact skill you'll use to supervise an AI. When Claude Code says "I'd like to move these files," you'll know how to peek first (ls) and decide for yourself whether it's pastry pictures or your W-2.
You just learned the five words you and your AI now have in common.