a map of backend systems

About

Learning in public, one system at a time.

Every article here starts as a personal study log: a syllabus, a set of pass/fail checks, and a running list of the things I got wrong and had to relearn. When a topic clicks, I rewrite those notes as a deep-dive meant for someone standing where I was a few weeks ago.


How each deep-dive is built

model
Mental model first — before any API, the one idea that makes the rest make sense.
rubric
Each section maps to a concrete "can you actually do this?" check, not just exposure.
gotchas
The Gotcha notes are real mistakes from my review queue — misconceptions that cost me a session to unlearn, so they cost you a minute.
verified
Version-specific facts are checked against current docs before publishing.

The goal isn't a reference you skim — it's understanding you keep. If a section can't survive being explained back in your own words, it isn't done.

— duthaho