Tags: web-dev map

Languages MOC

Date: 2026-08-16


One folder each. Each holds a reference — the language mapped rung by rung — plus concepts for the durable models that language exposes better than the others. What belongs here: the reference, and concepts genuinely about that language’s model. What doesn’t: patterns expressible anywhere, which are Foundations. A closure is a JavaScript note; a state machine isn’t.


JavaScript

The one that has to be deepest, because everything client-side runs through it.

TypeScript

CSS

PHP

C#

Liquid

  • Reference - Liquid — the language mapped, Shopify flavour, base-gem differences marked

SQL

  • Reference - SQL — the language mapped
  • Joins — the four kinds, drawn as row sets rather than described
  • Window Functions — computing across rows without collapsing them; the tool most analytics work actually needs
  • Common Table Expressions — naming intermediate results, and readable recursion
  • Aggregation and Grouping — GROUP BY, HAVING, and the ordering of evaluation that explains most errors
  • Query Performance — the handful of rewrites that fix most slow queries, and why warehouse cost is bytes rather than time
  • SQL Dialects — where Postgres, MySQL, BigQuery and SQLite diverge on things you’d assume are standard

Borders

Filed elsewhere, needed constantly here.