Start.dev
Back to blog

What to do after you finish your first course

What to do the week after you finish a short course: review what you built, pick one next course, and do not start three new ones.

Ariel Weinberger
Ariel Weinberger · 6 min read

You just finished your first coding course. Now what?

Short answer: spend a week making what you learned stick before you start anything new. Rebuild one piece from a blank file, change your project so it is yours, write down what is still fuzzy, then pick one next course and only one.

The week after a finish is where a lot of learning quietly leaks away. You feel done, so you stop, or you get excited and open three new courses at once. This post gives you a simple plan for that week instead. It uses CSS Basics as the example, but the same steps work after any course.

Why the week after matters

Finishing a course means you followed every step and it worked. That is a real achievement. But following along and building from scratch are different skills.

The gap shows up the first time you open an empty file with no instructions. If you move straight on to the next course, that gap never gets tested, and it is still there months later. If you stop entirely, you forget faster than you expect.

A week of light, focused practice closes most of that gap. You don't need to study for hours. Thirty to sixty minutes a day is enough. How to practice coding when you only have an hour has a format for those sessions.

Day 1: look back at what you built

Open the project you finished at the end of the course. For CSS Basics, that is the page you styled and polished in Fluid Type And Polish (opens in a new tab) before the Wrap Up (opens in a new tab).

Go through it slowly and, for each part, ask one question: could I explain why this works?

Mark anything where the answer is no. Maybe it is why box-sizing: border-box changed the layout, or why one flex item grew and another didn't. That list is your study plan for the rest of the week.

Day 2: rebuild one piece from a blank file

Pick one part of the project, not all of it. A navbar, a row of cards, a single section.

Close the course. Open an empty file. Build that piece again from memory.

You will get stuck. That is the point. Every time you have to look something up, you have found a gap the course hid by giving you the next step. Look it up, write it down, and keep going. How to escape tutorial hell explains why this step matters so much.

Day 3: change it so it is yours

Now take your project and make it different. Small changes are fine:

  • Change the color palette and the font.
  • Add a section the course didn't have.
  • Make it work at a screen size you didn't test.
  • Turn it into something real, like a page about a hobby, a menu for a friend's café, or a simple personal page.

Changing a project forces you to understand it. You can't move a section without knowing how the layout holds together.

Day 4: go back over the fuzzy parts

Take the list from Day 1 and the lookups from Day 2. Go back to just those lessons and redo the exercises.

For CSS, the parts people most often need a second pass on are the box model, flexbox and positioning. Rewatching an entire course is slow and mostly repeats what you already know. Targeted review is fast.

Day 5: write down what you learned

Write a short note, for yourself or as a post, with three parts:

  • What I can do now that I couldn't before.
  • What I still find confusing.
  • What I want to build next.

This takes fifteen minutes and does two jobs. Explaining something in your own words is one of the best ways to remember it. And the last line tells you which course to pick next.

Then pick one next course

Only one. Choose it based on what you want to build, not on what sounds impressive.

After CSS Basics, a natural next step is Tailwind CSS Basics (opens in a new tab). It uses everything you just learned, padding, margin, colors and flexbox, but writes it as small classes in your HTML. Knowing the CSS underneath makes Tailwind's class names obvious. Tailwind CSS vs CSS for beginners explains how the two fit together.

If you would rather make pages do things, the other natural path is JavaScript Basics (opens in a new tab), which adds logic and interactivity.

If you want to...A sensible next course
Style pages fasterTailwind CSS Basics
Make pages interactiveJavaScript Basics
Structure pages betterHTML Basics, if you skipped it

Why not three courses at once

It is tempting. You have momentum, and everything looks interesting. But three half-finished courses teach you less than one finished one, and they make it harder to tell which one is helping.

A finish is also a good feeling worth repeating. One course at a time means you get that feeling again sooner.

Common mistakes

  • Jumping straight into the next course. The gaps from the first one come with you.
  • Stopping completely. A week off turns into a month quickly. Keep a short session going.
  • Rewatching the whole course. Review only the parts you marked as fuzzy.
  • Starting a huge project. A full app is too big right now. Change the project you have, or build one small piece.
  • Choosing the next course by hype. Pick the one that gets you closer to what you want to build.

Quick recap

  • Spend the week after a finish making it stick, not starting something new.
  • Look back at your project and mark what you can't explain yet.
  • Rebuild one piece from a blank file, then change the project so it is yours.
  • Review only the fuzzy parts, and write a short note on what you learned.
  • Pick one next course, based on what you want to build.

Frequently asked questions

Should I start a new course right after finishing one?

Give it a few days first. A short week of rebuilding and reviewing makes the first course stick, and the next one goes faster because of it.

How do I know if I really learned the material?

Try building part of your project from a blank file without the course open. If you can, you have it. If you get stuck, those are the parts to review.

What should I learn after CSS?

Tailwind CSS if you want to style faster, or JavaScript if you want to make pages interactive. Both build directly on what CSS Basics teaches.

Is it bad to forget things after a course?

No. Everyone forgets some of it. Rebuilding and changing your project is what moves it into long-term memory, and looking things up is a normal part of coding.

How long should I spend on review?

About a week, at thirty to sixty minutes a day. Longer than that and you are probably ready to move on.

Practice

Open your finished CSS Basics project and start Day 1 today. If you haven't finished the course yet, Welcome (opens in a new tab) is where it starts, and everything runs in your browser, so there is nothing to install. When the week is done, the next step is Welcome (opens in a new tab).

Keep going

CSS Basics (opens in a new tab) takes you from your first rule to flexbox, grid and responsive layouts. Tailwind CSS Basics (opens in a new tab) picks up right where it leaves off.

Level up your coding skills

Jump into interactive courses and start building real-world projects.

Start learning

Related posts

Stuck watching tutorials but unable to build alone? Learn the four causes of tutorial hell, how start.dev solves each, and a weekly routine to break out.
Ariel Weinberger
Ariel Weinberger · 6 min read
A one-hour coding practice you can repeat on a weeknight: recall, one exercise you write, a short note, and a start line for tomorrow.
Ariel Weinberger
Ariel Weinberger · 7 min read
Should beginners learn Tailwind or plain CSS first? See the same card built both ways, what Tailwind assumes you know, and a learning order that works.
Ariel Weinberger
Ariel Weinberger · 5 min read