Charts for people who write code
These are not tutorials. They are the things you know perfectly well and still look up: which redirect preserves the method, what flex: 1 actually expands to, whether a change is in the working tree or the index, how many bytes someone means by a gigabyte.
HTTP status codes are grouped by class rather than listed in numeric order, because that is how they are reasoned about. Flexbox is split into what belongs on the container and what belongs on the item — the distinction people actually get wrong. The Git sheet draws the places a change can be sitting between your editor and the remote. And the data units sheet runs from the bit upwards, where the same word keeps meaning two different numbers.
They belong on the wall of a study or a small office: the kind of reference you glance at without breaking a train of thought to open a browser tab.
PERCENT-ENCODING IN URIs
128 ASCII positions: 66 unreserved, 18 delimiters, 43 that must always be encoded — and the "%" itself
THE UTF-8 ENCODING
how a Unicode code point falls into one, two, three or four bytes — and which bytes never appear
UUID
thirty-six characters: where the version sits, where the variant sits, and what each of the eight versions is made of
VIDEO CARRIERS
nine formats at true scale — and the frame that kept growing after the carrier stopped
VIDEO FORMATS
who published each standard, when, the names it goes by, and what has to be squeezed
VIM COMMANDS
modes, motions and editing per the Vim 9.1 help — and the grammar that composes them into commands
WORD EXPANSION
Four steps in a fixed order — and only two of them can change how many fields reach the command