# How This Course Works

How Node.js in Depth works on ask-codey.com, from reading a lesson and trying its Do It to exercises checked by tests, chapter checks, module assessments and the projects you build.

Novice · Node.js · JavaScript · Updated November 19, 2026

By Gregor Dzierzon

## After this lesson you can

- Describe how this course's lessons, Do Its, Check yourself blocks, exercises, chapter checks, module assessments and projects fit together

## Key takeaways

- The course has six modules. Each one ends with a mini-capstone, a project of its own, and an assessment that passes at 80%, with three tries a day.
- Skills are short "you can do this" statements. They are what the questions test and what your progress counts.
- A wrong answer in Check yourself is useful news, not a failure. Read the explanation, look back at the lesson, and carry on.
- An exercise comes with tests, programs that check your code. npm test runs them, and the exercise is done when every test passes and you've handed it in.
- Covered counts the lessons you've finished. Mastered counts the skills you've shown you know, with three clean answers to questions that come at each skill from at least two different angles.

This course is self-study: you go at your own pace, and the course itself tells you how you're doing. Here is what it's made of, and how to get the most from each part.

## The shape of the course

| Part | What it is |
|---|---|
| **Module** | A big stage of the course, ending with a project. This course has six. |
| **Chapter** | One subject, such as Getting Started with Node.js or Testing an API |
| **Topic** | A group of lessons inside a chapter |
| **Lesson** | One idea, explained with small examples you can run |

The six modules, and the project each one ends with:

| Module | What you learn | The project |
|---|---|---|
| 1. Meet Node.js | Running programs, the JavaScript Node leans on, modules, npm, the debugger, files and the command line | Expense Tracker CLI |
| 2. Building Web APIs with Express | HTTP, web servers, REST APIs with Express, validation, errors and tests | Library Loans API |
| 3. Data with MongoDB | Keeping an API's data in MongoDB: saving, finding, changing and testing it | Recipe Box API |
| 4. Users and Security | Passwords, signing in, who may do what, and protecting an API | Club Events API |
| 5. Real-Time Apps | Live updates with WebSockets, big files, uploads and work that runs later | Live Quiz Night |
| 6. Professional Node | Logs, configuration, code quality, tests on every push, and an API online | Neighborhood Book Swap API |

Each lesson has a level from 1 to 4. Level 1 is meeting an idea for the first time; higher levels go deeper into the same subject.

## Skills, Do Its and Check yourself

Most lessons start by listing their **skills**: short "you can do this" statements, such as *Run a JavaScript file with the node command*. Skills are what the questions test, and what your progress counts.

Many lessons have a **Do it**: a small task in the lesson's own example, solved in a box right on the page, with tests that tick as your code works. Lessons whose point is Node itself, such as files or servers, need Node on your computer instead, so their chapter's exercise is where you practice.

Near the end of a lesson, a **Check yourself** block asks one to three short questions about what you just read, then shows you the answer and why. If you get one wrong, that's useful news, not a failure. Read the explanation, look back at the lesson, and carry on.

## Exercises

Lessons whose titles start with **Exercise:** give you a small project to finish: starter code in a repository on GitHub, and **tests**, small programs that check your code for you. You copy the starter to your computer with Git, open it in VS Code, and run the tests in its terminal:

```bash
npm test
```

`npm test` runs `node --test`, Node's built-in **test runner**: it finds the test files in the folder, runs them, and lists which tests pass and which fail. At first they fail, and that's expected: each part you finish turns its test green. From Module 3, the tests bring their own throwaway database, so you never set one up to check your work.

When every test passes, you hand the exercise in: you push your work to a repository of your own on GitHub and submit its address on the lesson page. That's what completes an exercise lesson. *Get the Exercise Code with Git* and *Hand In Your Work with Git* show each step.

## Checks, assessments and projects

- A **chapter check** is a short quiz on the chapter's skills, with a few questions from the chapter before to keep them fresh. Take it whenever you like, as often as you like: it's practice, and it tells you what to review.
- A **module assessment** ends each module. **80% passes**. You get three tries a day, then a 24-hour rest before the next three.

Every attempt draws different questions, so a retake is a fair new try, not a memory test.

- A **mini-capstone** ends every module: a project you build with everything the module taught, such as the Expense Tracker CLI at the end of Module 1. It comes with a brief, starter files, milestones that break it into steps, and a short checklist, called a **rubric**, that you score your own work against. None of them needs another one finished first.
- The **final capstone** is the course's final assessment, and there's no big final test. You design an API of your own, put it online, and write a README that explains how to use it.

## Covered, Mastered, and who gets what

When you're signed in, the course keeps two separate records of your progress:

- **Covered:** the lessons you've finished.
- **Mastered:** the skills you've shown you know. A skill is mastered when you answer three different questions about it cleanly, meaning right the first time and without a hint, and those questions come at it from at least two different angles: one might ask what a program prints, another which line to fix. A later miss drops it back, so mastery stays honest.

**Everyone** can read every lesson and answer its questions. **Signed in**, your answers count toward your skills, and you can tick lessons as done. **With Premium, or if you own this course,** you also get course progress on every page, the chapter checks, the module assessments, and the **Certificate of Completion**: every lesson covered and every module assessment passed.

A good rhythm: read a lesson and run its examples, try its Do It, answer Check yourself, do the chapter's exercise, take the chapter check, and when a module's skills are mastered, take its assessment and build its project.

## Check yourself

1 question to try on the lesson page.

## So what

The course is built so you always know where you stand: what you've read, what you've mastered, what to practice next, and what you've built.

## Key terms

- [Test Runner](https://www.ask-codey.com/glossary/test-runner)
- [node:test](https://www.ask-codey.com/glossary/node-test)

Source: https://www.ask-codey.com/lessons/node-how-this-course-works
