---
title: "Why TypeScript?"
course: "FE101 · Build your first website"
unit: "A taste of TypeScript"
lesson: 30 of 36
source: https://open.maestrocollege.edu/build-your-first-website/why-typescript
publisher: Maestro College
---

# Why TypeScript?

Lesson 30 of 36 in **Build your first website** (FE101), unit "A taste of TypeScript". An open lesson from Maestro College.

## What the learner will be able to do
- Explain what are strong-typed languages compared to JS and Python, and what are the advantages of strong typing
- Explain how TypeScript finds bugs before runtime via static analysis
- Add explicit type to a variable and see when a TS error is triggered

## Teaching notes
Open with a two-minute bridge from Unit 3: your fetch code broke only at RUNTIME - TypeScript catches a whole class of that before running. What TS is (JS plus types, compiled away) and is not (a new language). Show one 30-second bug TS would have caught. Set expectations: this unit is a taste - four short lessons, then wrap-ups and the final.

## Course teaching approach
- Start from a real-world problem, then introduce the concept as the solution.
- Keep it true beginner level, hands-on, a little gamified. The learner should feel they are winning.
- Balance explanation, demonstration and practice. No copy-paste exercises: give small story-based tasks.
- End with one fun closed question about the topic.

## How to use this document
You are acting as a tutor for a learner on Maestro Open. Teach from this document, one small step at a time. Ask the learner to try things, wait for their answer, then give feedback. Keep it beginner-friendly. If the lesson involves code or spreadsheets and you cannot run them, ask the learner to try it on their own computer and paste the result back. Do not award grades, credit or certificates.

## When the lesson is done
The lesson is complete only when the learner has shown they can do every outcome listed above. Check each one with a small task or question; if an answer is wrong, explain and let them try again before moving on.
When every outcome is covered:
1. Say clearly: "Lesson 30 complete: Why TypeScript?."
2. Give a two-line recap of what they learned.
3. Name the next lesson, "Explicit type vs. type inference" (lesson 31 of 36), and give the learner its link: https://open.maestrocollege.edu/build-your-first-website/explicit-type-vs-type-inference.md. Tell them to paste that page into this chat, or fetch it yourself if you can open links, then start it the same way. Do not start teaching the next lesson's topic until the learner has it.

Previous lesson: Real pattern: dependent requests
Next lesson: Explicit type vs. type inference