epid.co / writing / the journey Financial systems Writing Contact
← back to writing
The work record

Nine years of building,
measured rather than described.

Every figure on this page was computed from the repositories and the archive on this machine. Nothing is estimated, nothing is rounded up, and where the record is thin the page says so instead of filling the gap.

The totals

Commits authored by hand across the trading and financial repositories. Continuous-integration runners, image updaters and agent workers are counted separately and excluded from every figure below.

The platform, rebuilt seven times

The same product, written again from nothing, seven times, and the seventh is the one running now. Four of the six completed transitions were ended by something other than the code, and the bars are measured, not drawn: each one is what that rebuild actually produced.

Nine years, one grid

Every day since 2018, in a single unbroken record. The unit changes partway through, as it has to because the evidence does, but the timeline does not break, and neither did the work.

fewer commits file writes

Every project, 2018 to now

The catalogued record. Bars are coloured by domain; the shaded band is the period when nothing was built. Tap or hover a bar for what it was.

Scroll the chart sideways

Entries marked inferred have no recorded date. Their position comes from what the files contain, not from a timestamp, and is stated as a judgement rather than a fact.

The models

Every notebook and script in the machine-learning archive was opened and read, not counted. This is what they build: the architectures that appear in the code itself, and the trained weights they left behind on disk.

Deepest single files

Where the work went

Commits and code lines by domain. Code, documentation and data are counted apart, because a repository of research YAML and a repository of Go are not the same achievement.

Repositories

Newest first, so the most recent work leads. Any column will sort it: click a heading, or use the control just above the list on a small screen.

Repository Domain Commits Code lines Docs Median commit First Last Span

How these numbers were produced

So that any figure here can be checked, and so the ones that cannot be checked are marked.

    Rebuild the page with node build/harvest.js. It reads only commit metadata: author, timestamp, and per-file line counts. No file contents, no commit messages, and no repository names beyond the directory tree leave the machine, because nothing leaves the machine: this page is a local file.