Home

Entry point for the vault. From here, jump to any Map of Content (MOC) to navigate a topic area.

Maps of Content

A MOC is an index note: it links out to atomic notes on a topic. Browse via MOCs first, then follow wikilinks. 49 MOCs, grouped below; indented entries are sub-MOCs of the hub above them.

Linux and Operating Systems

The kernel, subsystem by subsystem. Start at the hub for the architecture, then dive.

Languages, Runtimes, and Compilers

Below the source line: how code becomes machine behavior.

Cross-Cutting Disciplines

Theory that applies everywhere and belongs to no single domain.

Data and Storage

Storage engines, query processing, and durability.

Distributed Systems and Architecture

Coordination across machines, and the system designs built on it.

Networking and Protocols

The wire: what travels, and in exactly which bytes.

Security

Primitives, identity, and securing the pipeline.

Infrastructure and Operations

Running it: orchestration, delivery, and reliability.

Machine Learning

Building models, serving them, and recommending with them.

Interview Preparation

The hub plus its two problem indexes.

Vault Conventions

  • One idea per note. Atomic notes link to each other; MOCs gather them.
  • Frontmatter on every note: tags, aliases, created, updated, sources.
  • Folders are coarse buckets, not the primary organization. Use links and tags.
    • Notes/ — atomic notes (the actual knowledge)
    • MOCs/ — Maps of Content (indexes that link out)
  • Wikilinks: [[Note Name]] — never raw markdown links for internal references.
  • Tags: kebab-case, nested where useful (#protocol/oauth2, #security/csrf).

Quick Searches

  • Notes flagged uncertain: tag:#uncertain
  • Recently created: sort the file explorer by created date, or query created:2026-05-*
  • All MOCs: tag:#moc

Open Questions Inbox

When something needs follow-up, add it here as a checkbox. Promote to a note when it grows.

  • none yet