How long does it take to learn Claude Code? A 15-day answer

The 15-sitting map is the planned curriculum for my Claude Code course. Each day is one sitting built around a different piece of the work. Right now, Sections 1 to 7 are live on Udemy. Sections 8 to 16 are still unpublished.

The planned map answers a better question than, "How many hours until I know Claude Code?" It tells you what you should be able to hold after each sitting when the full route is available.

Day 1 gives you a working picture of Claude Code and a decision about whether it belongs in your work. You watch a task manager built from one sentence on a bare setup, in real time. You do not install anything that day.

Day 2 puts Claude Code on your own machine. Day 3's planned outcome is a small portfolio site at a public address. Later planned days cover permission choices, cost, project rules, reusable skills, and connectors. They then move to several agents, scheduled work, design, client work, safety, and paid work.

The map does not turn 15 days into a universal promise. You may need more time to install the tool, choose a project, fix a problem, or understand a new word. The course divides the route by mental load, not by a stopwatch.

The Day 1 plan changed after the map was first written. It was first listed as 80 minutes and later measured at about 102 minutes. A route gives you an order. It cannot tell you how long your own questions will take.

You can use Claude Code from a terminal. A terminal is a window where you type commands for your computer. That name can sound technical before you have a reason to care about it.

Day 1 gives you that reason first. You watch a task manager take shape from one sentence on a bare setup. The tool creates the files while you watch. You then compare that small job with a task you already understand and decide whether to continue.

The outcome is modest on purpose. You should leave Day 1 able to say what the tool does and whether you want to learn the next part. You should not leave pretending you built something when you only watched a demo.

Installing a tool before you know the job can turn the first hour into a list of unfamiliar windows. Watching a job first gives each later step a reason.

Day 3 in the course is called Your First Real Project. The planned outcome is a portfolio site live on the internet, with an address you can send to somebody.

I checked the saved course project behind that claim. The portfolio lives in its own Git repository. Its public Vercel address returned a live page when I checked it. That proves the saved example reached a public address.

Your first site may take more time than the saved example. Your first page also does not need a recruiter-ready design. A small site makes a useful first project because you can open it in a browser, change one thing, and see what changed.

The project should be small enough that you can describe it before you begin. A personal page with an introduction, a few examples of your work, and a contact route is enough. A shop, payments, customer accounts, and a database can wait.

Keep your first version away from private customer data and irreversible work. Let Claude Code make changes in a folder you can inspect. Read the files. Open the page. Then decide what to change next.

The detailed course has many lectures. You do not need to memorise the names before you begin. The current course has a plain live route through Day 7, followed by a separate planned route.

The two tables separate what a current purchase contains from what is still planned. They also show why you do not need to learn permissions, prices, safety, and client work in your first session.

Choose one small project with a visible outcome. A portfolio page works because the result appears in a browser. A simple report page, a personal reading list, or a page for a local event can work too.

Write one sentence before you open the tool. Name the page, the pieces it needs, and the one change you want to see. Then make the folder. Ask Claude Code to help you build that one version.

When the tool finishes, do not measure the first run by whether it looked impressive. Open the page and ask four questions.

If you can answer those questions, continue. If you cannot, make the project smaller. You are learning a way of working with the tool, not trying to win a demo in one evening.

Anthropic’s official Claude Code overview is free to read and explains where the documentation begins. Read that first if you want current technical details.

Reading the documentation and running Claude Code are separate things. Anthropic says the Desktop app needs a paid Claude subscription. For the terminal and IDE routes, you need a Claude subscription, an Anthropic Console account, or a supported third-party provider before you can practise on your own machine.

My paid Claude Code course on Udemy currently gives you live Sections 1 to 7. The 15-sitting map is the planned curriculum, rather than the full route a buyer can take today. The live course is for the person who wants an order already chosen: a first project before advanced work, permissions before more reach, and safety before a client depends on the result.

You can also learn by opening the official documentation, choosing a small project, and moving slowly. You do not need a course to make your first folder. A course helps when you want the whole route and a reason for the order.