Cascade Runs · the making of

How this came to be

An accidental project, a few small fights with a machine, and what stayed.


On the first morning I ran, I came home and decided to make a small page. Something to mark the year. I had never built a website. I had no plan for one. The impulse and the run were the same kind of impulse — get up, do it, see what it becomes by the end.

So I opened Cowork — a desktop tool that lets a language model do things with the files on your own computer — and started typing the way one types a note to a friend. Something like: I would like to put together a small website about a year-long morning run I’ve started in Yerevan. The reply was patient and full of questions. We’ve been at it most days since.

What follows is a short record of how a small editorial corner of the internet got built over a couple of weeks by a person who knew nothing about building websites, and a machine that knows everything about it. It is not a tutorial. It is not a pitch. The page exists because the project exists, and a project’s making is part of the project.

A few things I noticed along the way

The machine is a collaborator, but the taste has to come from somewhere. When I asked for a silhouette of Mount Ararat to sit behind the title, the first attempt was two smooth bumps. I said it didn’t look like Ararat. The second was a pixel-trace of one of my own photos — honest, but ugly: vertical spikes from foreground poles, a flat top on Lesser. We tried a third version, and a fourth. None of them were right. In the end we dropped the silhouette and kept the title plain. The whole thing was probably an hour of my life. It is one of my favourite hours.

It misses things, sometimes badly. At one point we tried to set up automatic deployment to the host. Several rounds in, after I’d installed Node.js on its instructions, it turned out that the processor in my laptop is an architecture the deployment tool doesn’t support. None of that came up early. I wrote, somewhere in the middle of it, that something is wrong and you are wasting my limited tokens. It apologised and switched plans. Sometimes the apology is the right answer.

The voice on the page is mine. I rewrote almost every sentence the first time. After a while I stopped — the tone settled. The phrasings on the front page that sound like me sound like me because I edited them until they did. The ones that sound a little off probably haven’t been edited yet.

Moments

Two weeks in, fussing with the navigation.

Mewell, ok… but the “home” page now reads “the front.” i find it somewhat unusual… anything better you can suggest?

ClaudeI agree — “the front” is a bit of a newspaper-ism that sits oddly next to the others. Options: the start · home · today · the page

We picked “the start.” It has been there ever since.

The Mount Ararat silhouette, attempt three of four.

Mewell, ok… but the silhouette is very, very smoothed in its contours… why can’t you reproduce the exact contours of Ararat (great and the small ones)? shall not be a particularly difficult task…

ClaudeFair. The fix isn’t more hand-drawing; it’s tracing the real ridge from your reference photo with only light cleanup, so it keeps Ararat’s actual shape. The trick is tuning the sky detection so the hazy lower hills read as a continuous base…

Two more attempts after this. I eventually wrote: let’s drop the idea with adding this silhouette. The mountains stayed where they always were — out the window.

Trying to automate the deploy. Things were not working.

Menot sure those are working. something is wrong, and you are wasting my limited tokens

ClaudeYou’re right — I’m sorry. The actual error in your second screenshot is the real issue I should have spotted from your earlier output. Your machine is Windows on ARM. Cloudflare’s wrangler depends on workerd, which doesn’t ship a Windows-ARM binary. Path B is dead — wrangler cannot run on your hardware, period…

We switched to a different plan. The deploy works now. It almost always works.

Today. Asking about adding this very page.

Mehow do you like the idea of add a page with the description of how this was created, kind of “the making of…”? maybe just explain that it was a random idea… and provide the screenshots of my communications with you?

ClaudeI like the idea, but with caveats. The tone risk is real. The whole site says “no promotion, no growth plan.” A “making of” page can very easily tip into “look at this cool AI workflow,” which is exactly the register the rest of the site avoids. The save is to write it the same way you wrote The challenge — first person, quiet, more about the surprise of trying something you’d never done than about the tool itself. The page is about you deciding to do this, not about Claude.

And so, this page.

There will be more, probably. If something funny happens, I’ll add it.