How to make the most of this course

The most significant difference between learning from video and learning from text is that you have to be intentional about pacing. Video plays whether you're paying attention or not. Text requires you to choose what to do at each step.

Simply reading these lessons passively will not be enough. To truly internalize the skills of a web developer, you must engage actively with the material.

To get the best results, I recommend the following approach:

• Type the code, don't copy it: when a lesson shows you code, your instinct might be to copy and paste it. Don't. Your fingers learning the syntax — the spacing, the punctuation, where the brackets go — matters more than getting it right instantly. When you type it yourself, you catch mistakes faster and remember the patterns longer. Mistakes are where learning happens.
• Build alongside every lesson: read a lesson, then code the thing it teaches before moving to the next one. If a lesson is about adding a heading to a page, add that heading to your portfolio right then. Don't read three lessons ahead thinking you'll catch up later. Text-based learning requires momentum. Each lesson builds on the last, and falling behind creates confusion that's hard to recover from.
• Use your browser's developer tools to experiment: every modern browser has DevTools built in. Press F12 (or right-click and select “Inspect”). You can see the HTML structure, edit CSS in real-time and watch it change instantly, and run JavaScript in the console. When you read about how something works, stop and test it in DevTools. This transforms abstract concepts into concrete understanding.
• Don't skip sections because they sound simple: section 3 is about setting up your code editor. It sounds obvious. Skip it, and you'll be frustrated by missing settings that would have saved you hours. Section 5 is about semantic HTML — how to structure a page so it makes sense to both browsers and other developers. It feels basic compared to JavaScript. Skip it and your code becomes unmaintainable. Every section earns its place.
• When you get stuck, go step by step: a lesson teaches you to build a button with a click handler. Your button doesn't work. Your first thought might be, “I don't understand JavaScript.” More likely, you made a small typo or misunderstood one specific step. Open DevTools, check the console for error messages, and read them carefully. They tell you exactly what went wrong. Then re-read the lesson, focusing on the part that failed. If you still can't figure it out, move on and come back later. Sometimes your brain just needs to rest on something.
• Code is meant to be changed: after you build the thing the lesson shows, change it. Make the heading a different color. Swap the text. Delete a line and see what breaks. This isn't destructive — it's how you understand cause and effect. Every website you've ever visited started as someone changing and experimenting with their code.
• Download project files: you have access to the course project files, which you can download and compare against your own code. They’re a checkpoint, not a shortcut: use them when your portfolio doesn't match what a lesson describes and you can’t spot why. Resist opening them before you’ve tried to fix the problem yourself.

A note on AI tools

Tools like GitHub Copilot, Cursor, and Claude exist, and you'll almost certainly use them eventually. For this course, don't use them to generate the project code. Not because AI is bad — because the goal of this course is to build a mental model, and having AI write the code skips the part where the model forms. You can't evaluate whether AI-generated code is right, wrong, or quietly broken if you don't understand what it's doing. Once you finish this course, AI tools become genuinely useful — you'll know enough to direct them precisely and catch their mistakes. Before that point, they get in the way by hiding the learning.

Join the Discord community

Join the Mezie Labs community to get help and connect with other developers.

When you get stuck, past the point where re-reading the lesson or checking DevTools helps, the Discord community is where you post your question. Other students are working through the same material. Someone has almost certainly hit the same wall you're hitting, and someone else has already figured it out.

It's also where developers at different stages hang out. If you're a week in and struggling with the box model, there are people in there who were struggling with the same thing three months ago and can now explain exactly where it clicks. That's genuinely useful.

A few things that make asking good questions in the Discord (or anywhere) easier:

• Include the code that's causing the problem
• Describe what you expected to happen, and describe what's actually happening instead. This cuts the debugging time in half for whoever is trying to help you, including yourself.