Reference notes, organized as books

Pick two — but the interesting part is which two, and when.

CAP, consensus, partitioning, and replication — the four ideas everything else builds on.

The dozen codes that show up in real API design, and what they promise callers.

Ownership, traits, concurrency, and the questions that actually come up.

Move, borrow, or copy — the three questions that resolve most compiler fights.

Recon, the vulnerability classes that actually pay, privilege escalation, and reports that get read.