Measurements
Numbers that went up, and whether that meant anything.
Two things here count themselves without being asked. GitHub keeps a running total of stars; a small program on my laptop writes down what the machine is doing every 322 seconds. Neither was collected to prove a point.
Both are worth a page for the same reason. A running total only ever goes up, so it always reads as progress. The rate can be falling the whole time, and usually the rate is the thing you wanted to know.
Readings through rolled up page built
GitHub stars
A star is a bookmark, not a vote
Twelve years of stars across every repository, and what happens when you look at the arrival rate instead of the running total. The total only ever goes up; the rate has been falling.
Read it →Telemetry · Live view
Four months of readings from my laptop
The last 36 hours at full resolution: what the machine is doing right now, how much it is moving over the network, and how warm it is while doing it.
Read it →Telemetry · Week by week
The habits moved, and I didn't notice
The same measurements as the other telemetry pages, asked once a week instead of once. A working day that starts an hour later than it did in March, nights that got longer by the same hour, and one number that hasn't shifted at all.
Read it →Telemetry · Rhythm
What my laptop knows about my week
When the work actually happens, how sharply the weekend differs, and what a locked screen at 3am reveals about sleep. Four months stacked together show things no single day does.
Read it →Telemetry · Heat and pressure
My laptop is a thermometer for my office
Throw away every reading where the machine was busy and what is left measures the room, not the processor. Plus what a fleet of AI agents costs in memory.
Read it →Telemetry · Network
What the internet costs, depending on where I sit
Latency as a distribution rather than a line over time, measured from home, hotels, libraries, two airports and a plane. Public Wi-Fi has a reputation it does not deserve.
Read it →