Web Development
The browser first, the framework second. Eleven courses before any React appears.
- Courses
- 45
- Hours
- 68
- Modules
- 7
Between 2013 and today the default front-end stack changed four times. Each change threw away the specific knowledge and none of the underlying knowledge.
Students regularly tell us the first eleven courses felt slow. The same students tell us, four months later, that it was the part that made everything after it fast.
The sequence
Modules unlock in order. You finish one before the next opens, which is the point of a path rather than a playlist.
-
01
HTML that means something
Elements as an accessibility and SEO decision, not a div habit.
-
02
CSS layout properly
Flexbox, grid, containing blocks and stacking contexts.
-
03
The DOM and events
Bubbling, delegation, and why that listener in a loop behaves the way it does.
-
04
HTTP and the network tab
Requests, caching headers, and reading a failing preflight.
-
05
The event loop
Microtasks against macrotasks, and why your promise resolved late.
-
06
Then a framework
React as a set of re-render decisions you can now reason about.
-
07
Typed and tested
TypeScript and the tests that make a codebase survive other people.
What you can do afterwards
The assessment checks these directly, against a rubric published before you start.
Before you start None, but expect the first month to be about the platform rather than about libraries.
- Rebuild a framework feature with no framework, and know what you lost.
- Debug from the network tab instead of from guesses.
- Read a React re-render and explain it.