Update 80: The 07:12 to Haarlem was on time. I do not know how to process this emotionally.
Jade Wolters
If it fits in 280 characters I might be wrong, but I will be brief.
This should be in the house rules. People keep rediscovering it. [117.3]
Update 123: Tried the long way around Naarden on the bike. Extra twelve minutes, minus two close calls.
This should be in the house rules. People keep rediscovering it. [92.3]
Same energy as the 03:12 outage, but daylight this time. (37)
This should be in the house rules. People keep rediscovering it. [67.3]
I am quoting this later. Too clean a summary to lose. [117.4]
Roaster in Oostvaardersplassen asked how I wanted it. I said “like the 11:00 train: late but intense”. They understood.
I am quoting this later. Too clean a summary to lose. [92.4]
Update 81: Stopped using a CDN in front of a static site. Latency went up, bills and mystery headers went down.
Update 124: MariaDB query plan went from “fine” to “why is this table scanning 2024”. Indexes are a lifestyle.
Update 82: Found a bench in Eindhoven that is not next to a speaker. I am not telling you which one.
Update 125: Quiet evening in Hilversum. Someone is practicing saxophone and they are almost good. Rooting for them.
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [78.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [53.1]
Update 83: Work identity thought of the day: private spaces should leak nothing. Not even the joke.
Update 126: Registrar panel just showed “pending” in four languages. Internationalisation of despair.
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [28.1]
Do you have a ticket number? The public status page is lagging again. [78.2]
Do you have a ticket number? The public status page is lagging again. [53.2]