Site experiment · first seen July 11, 2026
Build Rhythm
A public record of building cadence without pretending commits, changed lines, or tokens measure productivity. The page keeps GitHub history and recent Codex use on visibly different clocks, then lets visitors inspect the exact aggregate values.
How can a public activity page show cadence and change without turning them into a score?
Weekly commits, additions, and deletions stay separate from a dated 30-day Codex snapshot.
No repository names, raw account events, cost theater, causal claims, or productivity ranking.
Origin
The first version began as a research-grounded activity workbench. John Thompson later shared The Rhythm of Food during an HCI intern design session about balancing performance, interactivity, and effort across SVG, Canvas, and WebGL. The transferable lesson was pacing: reveal one relationship at a time, then hand the reader the exact record. This site adapts that narrative principle to aggregate build data without copying its visual language or code.
What the page protects
Commits describe cadence. Additions and deletions describe the magnitude and direction of a change. Tokens describe a separate record of recent tool use. None of them explains quality or cause on its own, so the interface keeps units, horizons, and provenance visible instead of morphing them into one synthetic score.
-
b4203f3eaIntroduced the activity view with keyboard inspection, an exact table, and a privacy-safe fallback. -
ed0d3ba40Separated the Codex and GitHub horizons after one combined overview implied a relationship the data could not support. -
d3f13be35Removed causal and cost clutter so the evidence returned to cadence and change. -
1b07cea4cRestored additions and deletions with readable and literal scales plus stronger responsive evidence.
Credits
The Rhythm of Food was made by Google News Lab and Truth & Beauty. Thanks to John Thompson for sharing it and starting the conversation about storytelling across web rendering systems.