Languages
Language and runtime depth — one folder per language, each holding subtopics tailored to how that language is actually used (Localz's stack, and broader professional breadth for job-market purposes).
Why we need this / what value this brings
General topic folders like ConsistencyConcurrency/ or Networking/ cover language-agnostic theory; this is where that theory gets applied through a specific language's idioms, stdlib, and ecosystem — the layer a code review or interview actually tests.
When to use this
When a note is specific to how a language implements a concept (e.g. Python's GIL, Go's goroutine scheduler, TypeScript's structural typing) rather than the concept in the abstract.
How to use or implement this
Cross-link back to the general topic folder for theory (e.g. Languages/Python/Concurrency/ links to ConsistencyConcurrency/Concurrency-Threading/), and keep language-specific application here.
Subtopics
- Python — Localz's backend language (FastAPI)
- Go — not in the Localz stack; platform/infra breadth (Kubernetes, Terraform, SRE tooling)
- TypeScript — Localz's frontend language (Next.js), plus the broader Node ecosystem
Related
- ConsistencyConcurrency — general concurrency theory
- FrontendWebMobile — general frontend theory
Empty folder — drop notes, links, and findings here as you research.