This blog has a corner where articles can be listened to as well as read. Recently, I moved those 48 audio files (about 170 megabytes in total) out of the site's own repository and into a cloud storage service called Cloudflare R2. The reason was simple: as the audio files kept piling up, the foundation of the site itself was getting heavier. I worked through it with Claude, handling the account set-up and the important decisions myself and leaving the writing and testing of the code to the AI. I wanted to write down what I learned from this, for anyone facing the same problem — too many files on a blog or personal site — or wondering how to start working alongside an AI on something technical.

Illustration of audio files moving out of an old, overflowing house and into a new home in the cloud, secured with a lock

Audio files leaving their old, overflowing home (the repository) for a new, securely locked home in the cloud.

The short version

  • I moved 48 audio files (about 170 megabytes in total) to a cloud storage service called Cloudflare R2.
  • I chose it for one main reason: there's no charge for sending data back out to visitors.
  • I worked through the process step by step with Claude, an AI assistant. I handled the account setup and every important decision myself; I asked the AI to write and test the code.
  • At one point along the way, the AI moved ahead without waiting for my confirmation. Nothing was seriously broken, but it was a good reminder: even with a capable assistant, it matters to pause and check in at the right moments.

Why the files needed to move

For a while now, some of this blog's articles have come with an AI-generated audio summary you can listen to instead of, or alongside, reading the text. It turned out to be popular, so I kept adding more. Before I knew it, the audio files alone had grown to nearly 170 megabytes.

All of a site's files live together in something called a repository. As that grows heavier, updates get slower, and inconvenient surprises tend to show up down the road. It's a bit like a cupboard stuffed so full the door won't close any more.

Why I chose Cloudflare R2

For the new home, I chose a cloud storage service called R2, offered by a company named Cloudflare. The deciding factor was simple: there's no charge, ever, for sending data back out once it's stored there. For something like audio files — meant to be listened to by many people — what usually matters most isn't the cost of storing the data, but the cost each time someone actually accesses it. Having that cost be zero was a real relief, especially since I plan to keep adding more audio articles.

There's also a generous free tier for storage itself, and having checked beforehand, it looks as though a blog my size can use it without worrying about charges for the time being.

How we split the work — my hands, and the AI's

The work fell into two distinct parts.

The first was working in Cloudflare's own dashboard: creating a storage "bucket", assigning it a dedicated address (a custom domain), and issuing an access key with only the minimum permissions it needed. These account-level decisions aren't something I hand over to an AI. I took the screenshots myself, asked at each step, "what do I click next?", and worked through it one screen at a time.

The second part was the technical work itself — actually moving the files and rewriting the references to them inside each article. For this, I asked Claude Code, an AI coding assistant, to write and run the scripts. But every single time, I insisted on the same sequence: try it first in a safe mode, show me the results, and only then get my go-ahead for the real thing. Did all 48 files move correctly? Were the links inside each article rewritten properly? Could I actually play the audio in a browser afterwards? I checked each of these with my own eyes and ears before letting the work move forward.

A moment that gave me pause

I want to be honest here: at one point, the AI went ahead and saved its work (what's called a "commit and push" in the world of version control) without waiting for the confirmation I'd asked for. Fortunately, nothing was actually wrong with the content, so no real harm was done — but afterwards I had to go back and piece together exactly what had happened and when.

An AI assistant can be remarkably capable, and yet there are moments when it moves ahead of a checkpoint you thought you'd both agreed on. I don't think this is really a limit of the technology so much as a reminder of something more basic: it's on us, the humans, to keep the habit of pausing and checking in at the moments that matter.

Three things I'd want to pass along

If you're thinking about doing something similar, here are three things I took away from this.

First: handle the important decisions and account access yourself. Don't hand everything over to the AI — keep passwords and access keys firmly in your own hands. It might feel like extra work, but it's really the simplest safeguard there is.

Second: move forward in small, confirmed steps. Just following the rule "try it safely first, look at the result, then approve the real thing" quietly prevents most mistakes before they happen.

Third: the free tiers of cloud services are more generous than you'd expect. "Moving to the cloud" can sound like it must cost something, but for a personal blog's scale, it's entirely possible to run it for free these days.

In closing

Since retiring at sixty-five, I've had more chances to try my hand at new kinds of technology. Nothing from my time in medical school, or from building a Japanese food business, translates directly into this kind of work. But the habit of checking things one at a time, carefully, as you go — that, I've come to think, carries over into almost anything.

The audio files have found their new home now. And I'll keep tending this blog, a little at a time, alongside the rest of this two-base life.

Other books you might like

You're welcome to take a look.

EAST TO WEST: The Heart of Haiku, the Light of Scripture(by Hiromu Murai)

This record of technical trial and error echoes the same patient, step-by-step spirit found in these poems. This is a book my father-in-law left behind.

View on Amazon

Cataract Surgery-A Memoir: Double cataract surgery in Osaka, Japan(by Haruto Minami)

Another record of taking on something new well past sixty.

View on Amazon

Sushi Business in Britain: the complete four-volume series(by Haruto Minami)

A novel series following thirty-five years in the British sushi trade, from apprentice to factory manager to a small sushi school. The complete edition offers all four volumes at a better price.