JavaScript, by building things
No "what is a variable". Just real projects, learned by shipping.
Tutorials · Implementation first
Most courses teach concepts before you have anywhere to put them. Here we do the opposite. Each tutorial is a build — a calculator, a chat, a login flow — and the concepts arrive at the moment the build demands them. By the end you have working software AND you understand why each piece works.
Build first
Every lesson produces working software. You learn the language by needing it.
Concepts in context
Variables, types, async — introduced the moment the build calls for them. Then catalogued.
AI-augmented
Traditional craft and AI-augmented practice, side by side. Prepare for both careers.
Learning paths
No "what is a variable". Just real projects, learned by shipping.
Build a real login flow. Sessions, password hashing, the works.
The skill set that defines the next decade of software.
Hand-picked builds
A working calculator. Type a number, an operator, another number, hit equals, get the answer. Same logic that powers the calculator app on your phone.
A page becomes alive the moment JavaScript listens for an event and changes the page in response. Build a counter, then open it in /code.
Python reads almost like English. Write a small converter, see its output, and open the project in /code to keep editing.
Two equal tracks
Build it, then learn what made it work.
Build your first web page
Hand-write a small, semantic page — a heading, a paragraph, a list — then open the same project in /code and make it yours.
Your first C++ program
C++ trades a little ceremony for a lot of speed and control. Write a first program, learn the compile-then-run cycle, and open it in /code.
Your first Go program
Go is small on purpose: a handful of keywords, fast builds, and one obvious way to do things. Write a first program and open it in /code.
Style a card with CSS
The quickest way to feel CSS: take a plain card and give it depth, spacing, and a button — editing the same project the Deep and Reference tiers use.
Build a clock
Thirty minutes, one HTML file, a digital clock that ticks. Along the way: setInterval, the Date object, and the first taste of the asynchronous mental model.
Understand the idea so every build clicks.
Arrays — reference
Arrays in JavaScript: indexing, mutation, iteration, the methods that survive the test of time, and the ones that do not.
CSS card — reference
One-liner reference for the card project’s properties — scan, copy, and open the live example.
CSS card — cheatsheet
The box-model card at a glance — the handful of properties that do the work, ready to copy.
Builds
Hand-write a small, semantic page — a heading, a paragraph, a list — then open the same project in /code and make it yours.
C++ trades a little ceremony for a lot of speed and control. Write a first program, learn the compile-then-run cycle, and open it in /code.
Go is small on purpose: a handful of keywords, fast builds, and one obvious way to do things. Write a first program and open it in /code.
The quickest way to feel CSS: take a plain card and give it depth, spacing, and a button — editing the same project the Deep and Reference tiers use.
Thirty minutes, one HTML file, a digital clock that ticks. Along the way: setInterval, the Date object, and the first taste of the asynchronous mental model.
Auth is one of those parts of the stack everyone uses and almost nobody has written from scratch. We are going to fix that. By the end of this tutorial you will have a working signup endpoint with real password hashing.
References
Reference · beginner
Arrays in JavaScript: indexing, mutation, iteration, the methods that survive the test of time, and the ones that do not.
Reference · beginner
One-liner reference for the card project’s properties — scan, copy, and open the live example.
Reference · beginner
The box-model card at a glance — the handful of properties that do the work, ready to copy.