TypeScript
Type-level patterns that make incorrect states unrepresentable, and the tradeoffs each one asks for.
content/typescript2 notes
Notes on using the type system to remove whole classes of bug rather than to decorate code that already works.
How this is organised
- patterns, modelling techniques, with the cost of each one stated plainly.
A pattern earns a note here when it changed how a real module was written, not because it is clever. Where a technique works worse than its reputation suggests, the note says so.