Types that catch real bugs without making the codebase unreadable.
Watch a free preview30-day refund, no questions asked
Training a team?
Volume pricing from five seats, with assignment, reminders and completion reporting included.
See team plans →Each maps to the same taxonomy your organization’s roles are defined in, so progress here moves your skill profile.
For engineers who know TypeScript syntax and want to use the type system as a design tool. Covers modelling domains with types, the advanced features worth the complexity, the ones that are not, and how to keep a large codebase's types maintainable across a team.
3 modules · 13 lessons · 7h 5m
Using the type system to make bad states unrepresentable.
Daniel writes the kind of frontend code that is still readable three years later, and he teaches accordingly. He is uninterested in framework tribalism and spends the first module of every course on the platform primitives underneath. Learners describe his rendering-performance lessons as the point the subject stopped being mysterious.
4,471 reviews
Genuinely good, with one caveat: the first module moves slowly if you already know the basics. Skip to module two if you do — the rest is excellent and the case studies are specific rather than generic.
Solid content, but I came in from a non-technical background and the assumed knowledge in module four caught me out. The prerequisites could be clearer about that. Everything before it was excellent.
Rolled this out to fourteen people. Twelve finished, which for us is unheard of. The pacing is right and nobody complained about the length, which is the real test.
The engineering around the model, which is where projects actually fail.
Anders Lindqvist · Arjun Mehta
18.9K
Measure, then fix — in that order, every time.
Daniel Roth · Ben Kowalski
47.1K
Designed around real postmortems, because that is where the lessons are.
Arjun Mehta
51.3K