How This Course Works

How Data Structures and Big-O, Demystified works on ask-codey.com, from choosing your language in the code tabs and running an exercise's tests to mastering a skill and passing a module assessment.

Novice · Data Structures · Software Development · Updated

By

After this lesson you can

  • Describe how the parts of the course fit together, from the language tabs and lessons to the exercises, chapter checks and module assessments

Key takeaways

  • The course has seven modules. Each chapter ends with an exercise, and each module ends with an assessment.
  • Every code sample comes in five languages, shown as tabs. Pick yours once, and every lesson opens on it.
  • An exercise is done when every test passes. You run the tests yourself, in your language.
  • Chapter checks are practice you can take as often as you like. A module assessment passes at 80%, with three tries a day.
  • 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. A few minutes here now saves guessing later, because every chapter works the same way. Here is what the course is 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. This course has seven: Why Organizing Matters, Things in a Line, Recursion, Searching and Sorting, Fast Lookup, Trees and Heaps, and Graphs, and Choosing Well.
Chapter One subject, such as Linked Lists or Hash Tables.
Topic A group of lessons inside a chapter.
Lesson One idea. It starts from a real problem, tries the plain fixes, and then shows the idea that works, with small programs you can run.

Each lesson has a level from 1 to 4: meeting an idea is level 1, working with it level 2, building with it level 3, and the advanced end level 4. A level says how deep a lesson goes into its subject, not how far into the course it is.

Five languages, one lesson

Every code sample in this course is written in C#, Java, Python, JavaScript and TypeScript. On the lesson page they sit together in one box, with a tab for each language. Click your language's tab once, and the site remembers it: every code box on every lesson opens on your language from then on. You can switch at any time, and nothing else changes.

The ideas are the same in every language, so each one is explained once, in words and pictures. Only the code changes. Each sample prints exactly the same lines in all five languages, so the output under the code is the same whichever tab you read. When a language does something differently (Python's numbers never overflow; JavaScript has no built-in priority queue), a short note under the code says so.

A lesson's code box with five tabs across the top, C#, Java, Python, JavaScript and TypeScript, with Python selected and its code and output showing below

You only need one language for the whole course. If you know two, flip between the tabs sometimes: seeing the same idea in another language is one of the fastest ways to learn it.

Skills: what you'll be able to do

Most lessons start by listing their skills: short "you can do this" statements, such as Count the steps a loop takes for a given amount of data. Skills are what the questions test, and what your progress counts.

Check yourself

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. Use them as a quick self-test: if you get one wrong, that's useful news, not a failure. Read the explanation, look back at the lesson, and carry on.

Exercises, and their tests

Lessons whose titles start with Exercise: give you a small program to finish, in a folder for each language. Each folder has your code to finish and tests: a small program that runs your code and says whether each part does its job. You download the exercise, open your language's folder in VS Code, and run the tests in VS Code's terminal as often as you like. At first every test fails, on purpose. When every test passes, you're done. Running the Exercise Tests shows the command for each language.

Exercises are where reading turns into skill, so don't skip them.

Chapter checks and module assessments

  • A chapter check is a short quiz on the chapter's skills, with a few questions that review the chapter before. 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. Most learners take an assessment more than once.

Covered and Mastered

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

  • Covered: the lessons you've finished.
  • Mastered: the skills and key terms 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. For a skill such as count the steps a loop takes, one question might show you a loop and ask what it prints, and another might ask how many steps a search makes on a playlist of 300 songs. Answering from two angles shows you understand the skill, not that you remember one answer. A later miss drops it back, so mastery stays honest.

Reading every lesson doesn't mean you know it, and the course never pretends it does. That's why the two are kept apart.

Who gets what

  • Everyone, signed in or not, can read every lesson and answer its Check yourself 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

  1. Read a lesson, and run its code in your language.
  2. Answer its Check yourself questions.
  3. Do the exercise at the end of each chapter, and run its tests until they all pass.
  4. Take the chapter check, and review the skills it points to.
  5. When a module's skills are mastered, take its assessment.

Try it. Look at this chapter's list of lessons. Find the exercise lesson at the end, and the chapter check after it: that's the rhythm every chapter follows.

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, and what to practice next, in the language you chose.