Matt Pocock Tutorial Covers Ten TypeScript Errors
Cryptic TypeScript errors waste hours. Matt Pocock's new tutorial isolates ten common messages from "Type Not Assignable" to "Property Does Not Exist" in interactive exercises. Clone the repo or use Gitpod to build debugging instincts instead of guessing.
Why it matters
Most engineering teams lose hours every week to cryptic TypeScript error messages. Junior developers guess and cast their way out of trouble, while senior engineers clean up any types in code review. Poor error literacy slows shipping speed and erodes type safety over time. When everyone reads errors differently, code review becomes a debate about syntax instead of logic. A shared vocabulary for common errors is one of the cheapest force multipliers a team can adopt.
What changed
Matt Pocock released a new interactive tutorial on Total TypeScript that isolates ten specific error patterns. The list includes Type Not Assignable, Property Does Not Exist on Type, Possibly Null or Undefined, Types of Property are Incompatible, Type Unknown, Expression of Type String Cannot Be Used to Index Type, Property Has No Initializer, Conversion of Type May Be a Mistake, Cannot Redeclare Block-scoped Variable, and Could Not Find a Declaration File for Module. Each lesson is built as an active exercise rather than a passive video. Learners clone a repo, read a problem, attempt a fix, and then compare against a provided solution. Gitpod integration means teams can run the exercises in a browser without local setup.
What to watch
Check whether your team's most frequent TypeScript errors appear in this list. If you are onboarding new developers, consider running the exercises in a group session to align debugging instincts. Also watch for follow-up workshops from Total TypeScript that move from error reading into advanced pattern design. The repo is public and the exercises cover both basic narrowing and module declaration edge cases, so it works for mid-level engineers as well as seniors who want to mentor more effectively.
Interview question
Why does the card say the tutorial uses active exercises rather than passive video?
- a.To let learners fix errors in a browser without needing local TypeScript setup
- b.To build debugging instincts and reduce reliance on guessing and type castingCorrect
- c.To provide a searchable reference guide for error messages during code review
- d.To cover both basic narrowing and module declaration edge cases in one sequence
Why? this is the answer
The card emphasizes that junior developers often guess and cast their way out of TypeScript errors, and active exercises are meant to build debugging instincts instead. Option A describes the Gitpod integration, which is a deployment convenience, not the pedagogical reason for choosing active exercises over video.
Just read this? Test yourself on what you have been reading.
Read the original → totaltypescript.com
- #typescript
- #tutorial
- #debugging
- #education
- #onboarding
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on typescript — each one lists the topics its interview covers.
See open roles