Tutorials, built to be
built along with.
We're structuring every tutorial track from the ground up - concept by concept, project by project - instead of rushing out another set of watch-and-forget videos. Here's what's coming, and why we're building it this way.
Reading docs teaches you facts. Tutorials teach you the order to use them in.
Figuring everything out alone from scattered docs and blog posts costs weeks that a structured path covers in days.
Without checkpoints, it's easy to practice the wrong habits for months before anyone tells you.
A visible path — what's next, how far you've come — keeps you going long after day-one enthusiasm fades.
Deadlines, edge cases, and broken builds teach things a tidy 'follow along' lesson never will.
Projects first. Video is the least of it.
A video lesson can explain a concept, but it can't tell you whether you actually learned it. Every tutorial we build is anchored to a project you ship yourself — watching is the smallest part of the process, not the whole of it.
| Video-only lessons | Our approach | |
|---|---|---|
| What you do | Watch someone else code | Write, break, and fix your own code |
| Feedback | None — you find out later, if ever | Immediate — your build either works or it doesn't |
| Retention | Fades within days | Sticks because your hands did the work |
| Output | A completed video | A working project in your portfolio |
| Confidence | Illusion of competence | Verified, tested competence |
Every module follows the same shape.
The video or reading is just the first step - the module isn't done until you've shipped something of your own.
Concept
|
Guided build
|
Checkpoint ─ are you actually following?
|
Independent challenge ─ no hand-holding
|
Shipped project ─ goes in your portfolio- 01Concept — the idea, in plain language, no jargon first
- 02Guided build — we build the first piece together, line by line
- 03Checkpoint — a small task to prove the idea landed
- 04Independent challenge — you extend it with no hand-holding
- 05Ship — the checkpoint becomes a real, portfolio-ready project
The tracks taking shape right now.
Nothing here is a placeholder - every track is being scoped, sequenced, and turned into real projects before a single lesson goes live.
Quick references for while you wait.
| Ask yourself | Green light | Red flag |
|---|---|---|
| Can I explain it in one sentence? | Yes, clearly | You need three tries |
| Is it slightly too hard? | Just past your comfort zone | Miles beyond it |
| Will you use or show it? | Yes — real motivation | No one will ever see it |
| Signal | You're watching | You're building |
|---|---|---|
| When stuck | You rewind the video | You read the error message |
| Typing | Copy-pasted | Typed from your own head |
| After a week | Can't rebuild it | Can rebuild it from memory |
How to actually get the value out of a tutorial.
Struggling for 20–30 minutes before looking something up is where most real learning happens — don't skip that discomfort.
Copy-typing a tutorial isn't the same as building it. Close the reference and try from memory before you check.
Ship something small every week. A finished small project beats an unfinished ambitious one, every time.
Read error messages fully before searching for them. Half the time the fix is in the message itself.
Track progress by what you can build unaided, not by how many lessons you've watched.
Getting stuck isn't a sign you're bad at this — it's the actual mechanism by which you get better.
We'd rather ship one track done right than five done fast. Check back for the first release.