Race report··5 min read·No. 132

Race Report: 58:12, 1,412th, Phone Called for Help Twice

Local 10K, bottom third of the field, two theft alerts, and a Friday at work I would rather not get into. Splits included, because splits are the point.

Behind the curtain+

Two stories on the same front page said the same thing from opposite ends. A phone classified its owner going for a run as a theft in progress, and the 207-comment thread argued almost entirely about London street crime rather than noticing that the classifier's model of a human body has two states, stationary and being robbed. Meanwhile AMD bought a company that etches model weights permanently into silicon, and under the demo link a commenter reported that his partner flatly refused to believe the answer was any good because it arrived too fast. Around those two sat a cluster all making the same argument about effort as proof: an essay on taste as the residue left when production stops costing anything, a piece on AI code and cooking steak, and forty thousand plays of a game showing that people waved through one threat in three. Mario Meets Pareto supplied a single word, dominated, and nothing else.

The center is that we do not believe in value we did not watch cost something, so the piece had to be built out of costs rather than claims. A race report is the only genre that is entirely receipts: splits, weather, shoes, what I ate, a number out of a larger number. The narrator is back of the pack and knows it, which lets Pareto sit invisibly as self-description rather than as something read. The phone alert and the etched chip share the same stretch of road because they are one idea, a machine failing a plausibility check because the cost was not visible. The Friday workday carries the taste, steak and rubber-stamping cluster in a single voice. The argument is never stated; the narrator buys the finish photo instead.

Long-time lurker, first race report. Bear with me.

Lead-up

Signed up in March during a period of what I would describe as optimism. Training block was eleven weeks on paper and about seven in practice. Missed most of June to a work thing. Longest run in the whole block was 8k and I walked part of it, which I am telling you up front so you can calibrate everything below.

Goal was sub-55. Stretch goal was sub-52. Actual was 58:12.

The week before was not great. I do backend work and Friday I shipped a feature I did not write. I want to be precise about this because I have been chewing on it: I did not write it, I read it, I asked for two changes, I got the two changes, and I shipped it. It works. It is fine. Nothing about it is wrong. It just is not mine in the way things used to be mine, and I spent the rest of the afternoon approving things at a rate I would not have believed a year ago. Yes, no, yes, yes, yes. There is a little history panel that shows you what the thing has been doing before it asks. I do not read the history panel. Nobody I have ever met reads the history panel.

My brother-in-law does a reverse sear. Two hours for a steak. He will tell you about the two hours before he tells you about the steak.

Anyway. I was carbing up on Saturday and reading an argument online about how the only skill anyone has left is taste, which the guy defined roughly as knowing what deserves to exist, and there was a line in it that got under my skin about how the market times you and the other guy with the same stopwatch and cannot see the difference between you. Which, sure. Except a race is the one place where the stopwatch is the whole point and everybody has agreed in advance that it is fair. Nobody at a 10k thinks the clock is missing something about them. Or if they do they have the decency not to post about it.

Gear

  • Shoes: the old ones. I have newer, faster shoes. I wore the old ones. I have no defence for this.
  • Socks: correct.
  • Shorts: incorrect, discovered at 4k.
  • Phone: on the arm strap, which turns out to matter.
  • Gel: one, at 4k, cherry, tasted like a candle.

The race

Field was 2,103. Weather was 14 degrees and flat grey, which is the best weather there is and I want to record that I appreciated it at the time rather than only afterwards.

The gun went and I went out too fast because everyone goes out too fast, and by the top of the first rise I had been passed by a man who I would put at sixty-five carrying what I am fairly sure was a small dog in a front-facing sling. I want to be clear that he was better than me in every measurable way that morning. Faster, smoother, more relaxed, and doing it with a dog. There was no dimension on which I beat him. Not one. I have a word for this from work, where it means an option you would never rationally pick because something else is better than it on every axis, and I spent most of the second kilometre applying it to myself and finding it fit.

Somewhere around 2k my phone buzzed against my arm in a pattern I did not recognise, and when I got it turned round enough to read it, the notification said something to the effect of: it looks like your phone was taken. Was this you?

I laughed hard enough to lose about four seconds. Then I thought about it for the next kilometre, which is the sort of thing you do when the alternative is thinking about your breathing.

Because here is the thing. Thursday night I had been messing with one of those demos, the new ones where the model is etched into the chip instead of loaded onto it, and it answers before you have finished reading your own question. It is genuinely startling. I showed it to my wife, who is not in tech and who has excellent instincts about people and none whatsoever about hardware, and she watched it produce four correct paragraphs in about a second and said, and I am quoting, how can it be thinking of a good answer if it comes that fast. I tried to explain. It did not take. I have thought about it every day since, and I was thinking about it at 3k with sweat in my left eye, because my phone had just made exactly the same call about me. Motion, no explanation, therefore something is wrong. It has a model of a person and in that model a person does not run unless something is behind them. She has a model of a mind and in that model an answer that costs nothing was not thought. They are the same instinct wearing different clothes and one of them is about to get baked into metal, at scale, permanently, and I do not know what to do with that except keep running.

We are going to end up putting fake delays into these things. I would put money on it. A little spinner. Two seconds of nothing, so it looks like it tried.

4k was the hill. Not a real hill. A hill by the standards of a course that needs a hill. I walked eleven steps and I counted them, which I offer as evidence that I was still basically fine.

Phone went off again at 5k. Same message. Second opinion, apparently.

5k to 6k is a long straight beside a car park and it is where I stopped having any thoughts at all, which I would like to note was the best part. Then the last stretch, and the noise, and a woman with a clipboard shouting a number that was not my number at somebody behind me, and the arch, and 58:12.

Splits

  • 1k: 5:12 (too fast, obviously)
  • 2k: 5:31
  • 3k: 5:44
  • 4k: 6:19 (hill, eleven steps)
  • 5k: 5:58
  • 6k: 5:47
  • Last 4k: I stopped looking. 23:41 by subtraction.

Chip time 58:12, gun time 58:44, position 1,412 of 2,103. Third from last in my age group at the club, which has eleven people in it and is not a serious club.

Notes for next time

Wear the new shoes. Do not eat the cherry gel. Do the long runs.

The volunteers were out there from six in the morning for a race with no money in it, handing water to strangers who were mostly not going to be fast, and one of them told me I looked strong at 5k, which was a lie told well, and it worked.

They emailed the photos on Sunday. There is one of me at about 5.5k where my mouth is open and my form has completely gone and I look, honestly, like a man being pursued. They wanted twelve euros for it, unwatermarked, high resolution.

I bought it.