The Tools, Demystified

Most of the fear around technical tools comes from unfamiliar words. Repository. Environment. Terminal. These sound like infrastructure. They're not. They're just names for patterns that already make intuitive sense.

This lesson strips the jargon and gives you a working mental model for each tool you'll encounter. You don't need to memorize commands. You need to understand what these things are for, so that when Claude generates instructions or explains an error, you're following along instead of guessing.

Files and Folders: You Already Know This

Your computer already has files and folders. A Python script is just a file — a text file with a .py extension. Nothing special happens to it until you run it. It lives on your hard drive like any other document.

When you're building a tool, you'll have a folder — let's call it your project folder — that holds everything related to that work. The script file, maybe a CSV of data it reads, maybe a config file with settings. All in one place.

The only new concept here is the repository. A repository is a folder that also tracks history. Every time you reach a point where the script works and you want to save that version, you record a snapshot. If your next change breaks something, you can restore the previous version instantly.

You don't need to use repositories to follow this track. But when someone says "push your code to a repo" or "clone this repository," now you know what they mean: they're talking about a folder with a history tracker attached.

The Terminal: A Conversation With Your Computer

A terminal (also called command prompt, shell, or console) is a text interface to your computer. You type a command. The computer responds. You type another command. The computer responds. It's a back-and-forth.

Two things make the terminal feel disorienting at first:

It remembers where you are. Unlike a file browser where you can see everything at once, the terminal always has a "current location" — the folder you're currently inside. When you type a command to run your script, it runs relative to that location. If the terminal is "in" the wrong folder, it won't find your file. This is the most common source of confusion for beginners.

Silence means success. When a command works, the terminal often prints nothing — it just returns you to the prompt. When a command fails, you usually get a message. So if you run a command and immediately see the prompt again with no drama, congratulations: it worked.

The Four Terminal Commands That Cover 80% of Your Needs

You don't need to memorize terminal commands — Claude will generate them for you. But knowing four will help you stay oriented:

Command	What it does
pwd	Print the folder you're currently in (works on Mac, Linux, and Windows PowerShell)
cd project-name	Move into the folder named "project-name"
ls (Mac) / dir (Windows)	List files in the current folder
python3 script.py	Run a Python script named "script.py" (python3 on Mac/Linux; on Windows, use python)

That's it. You type a command, press Enter, and the terminal responds. You are not programming the terminal — you are talking to it.

What "Environment" Means

You'll hear the word "environment" in two contexts:

Your environment refers to the software installed on your machine — Python version, any libraries you've added, your PATH settings. Two people with different environments can have the same script behave differently. When Claude asks "what version of Python are you running?", it's checking your environment.

A virtual environment (sometimes called a venv) is a self-contained box of just the packages one project needs. It keeps projects from stepping on each other. When you start a new Python project, creating a virtual environment is optional but good practice. Claude will tell you when and how.

Neither of these is complicated. "Environment" just means the collection of tools and settings available to your script when it runs.

What You Don't Need to Know Right Now

You do not need to understand:

• How the terminal is implemented
• What a shell "script" is (different from a Python script)
• Git commands beyond the concept of repositories
• Any Python syntax (yet)

The next lesson gives you the single most important skill for working with AI-generated code: reading it. Not writing it from scratch — reading what Claude produces, understanding what each part does, and verifying that it actually does what you asked for.

That skill is more valuable than memorizing any command.