Collections
/
- 1TypeScript, properlyThe type system as it actually behaves — narrowing, variance, and the operators people reach for without quite knowing why.14
- 2Cost & complexityEvery card that turns on a cost argument — time, space, or both. Short, and unforgiving about hand-waving.10
- 3Algorithms & data structuresThe classics, asked as questions rather than definitions. Why a structure behaves as it does, not just its big-O.12
- 4Systems & networkingProcesses, memory, caching and the parts of TCP and HTTP that come up in real debugging sessions.10
- 5Caching, everywhereThe same idea at five layers: memoization, LRU, the TLB, DNS TTLs and HTTP revalidation.5
- 6React & Next.js performanceVercel Engineering's React best practices as questions: waterfalls, bundle size, server rendering, re-renders and the hot-path details that add up.87
- 7React composition patternsVercel Engineering's composition patterns as questions: compound components, providers that own state, explicit variants over boolean props, and React 19's API changes.19
- 8Postgres & SQL in practiceIndexes, connection pooling, locking, row-level security, schema design and query patterns: the Postgres and SQL that holds up in production, on any host.61
8 collections