Why this design

Concept: Brendan Gregg's latency heat maps show what averages hide; the first screen makes my face the heat map's subject, built from requests and zoomed into the raw events, and an analyst reads one by zooming from the summary into the raw events; this page reads my work the same way, from where it happens to what it was.

Information architecture: sections are zoom levels ordered by resolution, career, years, days, events, and the sticky ruler is the navigation; the commit calendar is one view that opens a month's days in place rather than a second grid.

The years view is a density plot, one band per layer of the stack, built from my own classification of my roles and records; choosing a year there zooms the commit calendar to that year, and the months and days maps use the commit sample exactly as collected, with its caveat beside it; the events list ranks records by that evidence and then by result, so you can see that heat is not impact.

Honesty: the sample is capped at 200 commits per repository and skewed to recent work, saturated cells are marked, and employer work is shown as absent from the sample rather than imputed.

Type: Atkinson Hyperlegible Next and Mono, drawn for legibility, because heat maps are read at a glance and axis labels must survive small sizes.

Colour: one sequential ramp from pale peach to oxblood, the skin's own hue family; every cell also carries its number, so colour is never the only channel.

Motion: the portrait collects left to right because time does, and starts part-way so the first frame is already a heat map; every chart below is complete at rest, and only a month you select fills in, day by day.

Accessibility: the "Pause animation" button stops everything and then reads "Resume animation"; reduced motion shows each map complete; cells are buttons with written labels, months can be stepped with buttons or a menu, and nothing about you is stored.