Curriculum

Backend Depth

Closing the gap between "can build it" and "knows why it behaves this way under concurrency and failure." See MISSION.md for the full why.

Lessons

#LessonReference
1Why three indexes still weren't enoughIndexing cheat sheet
2The balance transfer that goes negativeIsolation cheat sheet
3When the cache expires and the DB falls overCaching cheat sheet
4Connection reuse and RTT costNetworking cheat sheet
5Blocking I/O and the schedulerOS cheat sheet
6The GIL and concurrency modelsConcurrency cheat sheet
7Retries and partial failureFailure models cheat sheet
8Why the table grows forever even though you're deleting rowsIsolation cheat sheet
9Why Postgres ignored your index and scanned the whole tableIndexing cheat sheet
10Why throughput collapses when the link saturatesNetworking cheat sheet
11Why the server says 90% memory used and nothing is leakingOS cheat sheet
12How one thread handles 10,000 connectionsConcurrency cheat sheet
13Why the queue that never fills up will eventually kill youFailure models cheat sheet
14How to retry a payment without charging twiceFailure models cheat sheet
15Why your own write is missing when you read from a replicaFailure models cheat sheet

Other

Start at Lesson 1, go in order. Ask follow-up questions on anything unclear — that's the point.