Collections
/
- 1SDE-IIAn onsite in fifty cards: React live coding and system design. State and effects, async JavaScript, Postgres, caching, API security and how to argue a trade-off, each checked against React's docs, Vercel's skills, GreatFrontEnd, OWASP and the System Design Primer.50
- 2TypeScript, properlyfrThe type system as it actually behaves — narrowing, variance, and the operators people reach for without quite knowing why.14
- 3Algorithms & data structuresfrThe classics, asked as questions rather than definitions. Why a structure behaves as it does, not just its big-O.12
- 4Systems & networkingfrProcesses, memory, caching and the parts of TCP and HTTP that come up in real debugging sessions.10
- 5Cost & complexityfrEvery card that turns on a cost argument — time, space, or both. Short, and unforgiving about hand-waving.10
- 6Caching, everywherefrThe same idea at five layers: memoization, LRU, the TLB, DNS TTLs and HTTP revalidation.5
- 7React & Next.js performancefrVercel Engineering's React best practices as questions: waterfalls, bundle size, server rendering, re-renders and the hot-path details that add up.87
- 8React composition patternsfrVercel Engineering's composition patterns as questions: compound components, providers that own state, explicit variants over boolean props, and React 19's API changes.19
- 9Postgres & SQL in practicefrIndexes, connection pooling, locking, row-level security, schema design and query patterns: the Postgres and SQL that holds up in production, on any host.61
- 10SDE-IIIThe follow-up questions, one level deeper: React internals, the JavaScript runtime, Postgres concurrency and migrations, distributed patterns, real-time and offline design, and auth security. Each card checked against official docs, OWASP, the AWS Builders' Library and the System Design Primer.49
10 collections