00:04By the end of this video, you'll have a professional AI workspace running on your
00:08own machine. The exact setup I use on real enterprise projects. 90% of tutorials skip
00:14this part, and that's precisely why beginners get stuck on day two. Not us. Let's build it.
00:20Quick hellos before we start. You've got four of us today.
00:23I'm Olga. I'm basically you, brand new to this. If something's confusing,
00:28I'll stop and ask so you don't have to. I'm Anastasia. When a new idea shows up,
00:34I'll explain it in plain language. No jargon walls. And I'm Sophia. I'll give you the exact steps in
00:40the exact order so nothing breaks. And I'll bring the why it matters in the real world,
00:45plus the live demo. All right, here's where we're headed. By the end of these 15 minutes,
00:49four things will be true. Python installed correctly, the S code, a real editor ready to go,
00:54a clean virtual environment, and your very first git commit.
00:59Okay, honest question. That already sounds like a lot for a beginner. Is it?
01:03It sounds like a lot. It takes about 10 minutes. And once it's done, you never do it again. That's
01:09the deal. A little care now buys you months of not being stuck.
01:12And you'll actually understand each piece, not just copy commands. That's the difference between
01:18following a tutorial and knowing what you're doing.
01:21Let me tell you the number one reason people quit learning AI. It's not the math. It's not the
01:26algorithms. It's a broken setup on day two, an error message that makes no sense and no idea why.
01:31That is exactly the thing I'm afraid of. I know. I've watched it happen for 20 years on real teams.
01:38So we're going to remove that fear entirely. We fix the environment once properly, and then it just
01:44works quietly in the background forever. Think of it like a kitchen. Before you cook anything
01:49impressive, you set up a clean counter and sharp knives. Skip that and every meal is chaos. Setup
01:57is the clean counter. Perfect. So let's set up our counter. Three pieces. Three things. That's it.
02:04Piece one, Python, the language every AI script is written in. It's the engine. Piece two, VS Code,
02:12the editor. It's where you'll write your code, run it, and see your mistakes clearly so you can fix them.
02:18And piece three, a virtual environment will call it a clean box. It keeps each project stuff separate,
02:25so they never interfere with each other. Wait, why would my projects interfere with each other?
02:31Great question. And it's the one everyone skips. On real projects, one app needs version one of a tool,
02:37another app needs version two. Without clean boxes, installing one breaks the other. I've seen whole
02:42teams lose a day to it. The clean box is how professionals avoid that from the start.
02:47So let's install these for real, switching to my screen. First, Python. Go to python.org,
02:53hit downloads, and grab the latest version for your system. I'll download it now.
02:57Stop. Before you click install. See this checkbox at the bottom? Add Python to path? Check it.
03:03This is the single most common setup mistake in the world, and it happens right here.
03:07What does add to path even mean? It just means, let your computer find Python from anywhere.
03:13Without it, you type Python later, and the computer says, never heard of it, even though it's installed.
03:20One checkbox saves you that whole headache. Installed. Now let's prove it. Opening a terminal.
03:26Python dash dash version cup, and there it is, the version number. That line means Python is
03:32installed and your computer can find it. If you see that, you're winning.
03:42And if I don't see it? Then path wasn't checked. Rerun the installer, choose modify,
03:48and tick add to path. That fixes it 99% of the time. Next, the editor. Head to code.visualstudio
03:55.com
03:56and download VS Code. It's free, and it's what a huge number of professionals actually use every day. Once
04:01it's open, go to the extensions icon on the left. It looks like four little squares. Search for Python,
04:07and install the official one from Microsoft. This extension is what makes VS Code understand Python.
04:12Highlighting, error hints, running your code with one click. Now I'll create one folder for our whole
04:17season. I'll call it build dash real dash AI and open it in VS Code. This one folder grows into
04:24everything
04:25we build. So everything lives in that one folder? Everything. One home for the whole journey. Now the
04:31piece most beginners never learn. The clean box. Let me show the idea, then we'll make one. Picture two
04:36sealed boxes. Project A has its own tools inside its box. Project B has its own tools in its box.
04:45They
04:45never reach into each other. That's a virtual environment. Isolation on purpose. Let's build one.
04:53In the VS Code terminal, type python dash m venv venv. That creates the box. Now activate it. On Windows,
05:03it's venv backslash scripts backslash activate. On Mac or Linux, it's source venv slash bin slash activate.
05:13And here's the tell. Look at the start of the terminal line now. See that little in front? That's your
05:18signal.
05:18You're safely inside the clean box. Any tool you install now goes in this box and nowhere else.
05:24So every time I start working, I just look for the venv? Exactly. No sh-fuck. You're outside
05:31the box. Activate it first. Make that a habit. Let's make the whole thing prove itself with a tiny
05:37first script. New file. Hello underscore ai dot py. A line to print a welcome message. And a line that
05:44imports a library and confirms it loaded. Now I run it. Run the file. Play button or python hello
05:51underscore ai dot py. Show the output in the terminal. And there's our output. That message
05:57printing means Python, the editor, and the environment are all working together, end to end.
06:02That's honestly kind of exciting. It's small, but it worked. That's the whole point. Most beginners
06:09never get past this moment. And you just did. On solid footing. One last habit. The one that quietly
06:14separates hobbyists from people who get hired. Everything we build goes into a Git repo.
06:20What's a repo in plain terms? A repo is a tracked history of your project. Every save point,
06:27called a commit, is a snapshot you can return to. And on a site like GitHub, it becomes something you
06:34can
06:34show people. By the finale of this season, this repo is a complete deployed project you can hand to an
06:39employer. It starts right now with one commit. In the terminal, git init to start tracking. Then one
06:47important line. Create a file called .gitignore and put venv in it so we don't upload that big box.
06:55Then git add dot and git commit with a clear message. And that's your first commit. The first brick of
07:00your
07:01portfolio. Beautiful. Let's lock in what you just did. Yubico. Python installed. Hand on your path.
07:09VS code with the Python extension. A virtual environment I can actually see. The little
07:16And a git repo with your first commit. That right there is a professional AI workspace. You're set for
07:23the entire season. Next episode, we write real code. I'll teach you the only Python you actually need for AI.
07:28Not a six month course. The five building blocks you'll use in every single AI script.
07:34That's the one I've been waiting for. If this got you set up without the usual pain, subscribe so the
07:39season stays in order for you. And drop your repo link in the comments. I read them, and I'll cheer
07:44you on.
07:45See you in the next one, Wizards.
07:47See you then.
07:47Bye bye.
