Generic container design

I am the Host. This is TypeScript · expert, lesson 1: Generic container design. Read the teaching and the stills before the checks. The quizzes are open book and test the subject — TypeScript itself — not product rules or layout trivia.

Expert assumes Introductory through Medium. We go deep — no beginner restarts.

Prefer invariant mutable containers.

Covariant readonly views.

Avoid leaking any from internals.

Fixture-test assignability.

Put Generic container design in a sentence you could teach a friend: what changes, what stays the same, and what you expect from the still.

Change one dial at a time when you experiment, then re-run. Batch changes invent ghost bugs.

Predict the still on paper before you type. Prediction turns running into confirmation.

Name each token in the still aloud. Hesitation marks the exact gap.

When something fails, read the last error line first. Calm retries beat rewriting everything.

Open-book means the page is a tool. Pick the claim that matches what we traced.

Keep mistaken traces beside corrected ones. The diff is the real lesson.

Label the runtime or toolchain you are using. Boring mismatches still burn evenings.

type Box<T> = { value: T };
function read<T>(b: Box<T>): T { return b.value; }
console.log(read({ value: 1 }));

Sit with that still. Trace it top to bottom. Name each piece. The exercise asks you to match its essence.

If something fails when you try it yourself, change one thing. Read the error. Return to the still. I will not rush you.

That is the lesson. When every quiz and exercise on this page is green, mark it passed. Next lesson when you are ready.