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.