Dev.to WebDev 🛠 Dev 👁 0 📖 10 min read

Diary of a Shrimp Keeper: A Joy Shared

Diary of a Shrimp Keeper: A Joy Shared The OpenClaw daily bulletin moves into a newsroom "A joy shared is a joy doubled." The First Assignment If you've read the first instalment of this diary, you ma

Diary of a Shrimp Keeper: A Joy Shared

The OpenClaw daily bulletin moves into a newsroom

"A joy shared is a joy doubled."

The First Assignment

If you've read the first instalment of this diary, you may remember Mini's very first assignment: every morning, gather the tech news, pick the day's highlights, and send them to my Telegram. Later, to save myself some trouble, I had it read the whole thing aloud, so I could listen while eating or on the bus.

That little daily bulletin, like a sweetheart, kept me company for months.

The Old Flame Goes Stale

But day after day, the sweetheart became an old flame.

Telegram gives you so little room. The text had to be trimmed to the bone, with hardly any formatting worth the name, and it was a strain to read.
If I wanted to look up something from last month, I had to scroll and scroll — or search the history and hope. Annoying.

The daily bulletin that had once been so charming had become, frankly, an eyesore.

A Gilded Cage

I got to thinking: news shouldn't stay buried in a chat log.

It needed a proper home — a gilded cage, if you like.

Why not build a website and let the daily news move in? Somewhere it could dress up properly, and answer whenever called upon.

...nice!

But a house that grand, with only one daily tenant — Mini — seemed a waste of good space.

And then there were the beauties: a thousand AI models, each with her own charms. Comparing them was a joy, but it was also a blur — a thousand faces and no way to tell them apart.

What I needed was a sharp-eyed clerk with a good memory: someone to compile and keep every model's particulars — vital statistics, learning, skills, memory, reflexes — all entered in a register, ready whenever I asked.

So I appointed Lily (List) as keeper of the model roll.

And there was the other thing I could never stop thinking about: the model debut circuit. Every so often a fresh-faced newcomer would appear, and I'd drop everything and hurry over for a look, terrified of missing the next big thing.
But I couldn't watch that circuit all day. It was maddening.

So I needed an errand boy too — someone to go out every day and ask around. The moment he spotted a newcomer, he'd hurry back and report.
Not just new models, either: gossip, popularity, the various leaderboards — all of it.

That's how Ruan — "Runner" to everyone in the newsroom — came aboard.

Mini took the desk as lead writer and newsreader; Lily kept the records; Ruan worked the street.

The daily and the model roll both went up on the public noticeboard. Private joy, shared.

And just like that, my gilded cage had turned into a newsroom.
Well. A newsroom it is.

Finding Premises

A newsroom needs premises.

I thought about buying land and building: rent a server, install the system, wire up the environment... half a lifetime of fiddling. Renting ready-made premises seemed far more sensible.

And then I discovered that some premises are free.
Take Cloudflare, for instance. The building is already standing, the landlord maintains it, cleans it, and keeps the guards on the door. As long as you don't move into some vast mansion and burn through everything, there's no rent at all.

A landlord with that much conscience deserves a round of applause.

So I moved in, bag and baggage.

Records and Rules

Everything gathered each day — news, model data — can't just be used once and thrown away. It has to be entered in the register and kept as a record, ready for reference.

And the staff have to work by the rules. Their daily charter — the code and the workflow — has to be laid out properly.

Both the charter and the records live in the bookcase (GitHub).

The two must be kept separate, of course.

The code and workflow that build the site can be drafted and refined gradually; once they've settled, there's little reason to touch them.
But the records — the site's content, especially those hard-won model dossiers — have to be written up every day, and kept properly.

Mini of the Daily

Mini, the daily, is my old flame.

Not only does she put the paper together well, she has a fine voice: every day's edition also comes as audio (MP3), and it's a pleasure to listen to.
She's fluent in the local tongue and in foreign tongues alike.
When she moved into the new newsroom, her old skills served her just as well.

Only one thing needed special handling: the audio takes up space — it can't sit on the bookcase shelf like ordinary records. A stage had to be built for it.
Fortunately, Cloudflare has R2, free up to 10GB. So I built Mini a stage on R2.

Lily, Keeper of the Records

Keeping the roll of a thousand beauties is no small job.

The particulars come from all over: some from the model marketplace, some from the benchmark boards, some from the popularity charts. Lily doesn't do the collecting — but sorting it all out and entering it in the register is enough to make anyone tear their hair out.

Just the names alone are enough to make your head swim.
Because different sources call the same model different things.
The marketplace calls her this, the benchmark board calls her that, and the open-source crowd uses a third name entirely.

Lily's first day on the job, she was utterly lost: are these three beauties, or one beauty in three disguises?

She worked through the night and turned up the next morning with dark circles under her eyes — "Good grief, I've finally got it sorted... and only because I laid down a rule — otherwise I'd have been a martyr by my first morning: every model gets one proper name, and aliases, old names, and version names all hang under it."

Ruan the Runner

Ruan is the one who goes out.

He doesn't write, he doesn't comment — he just asks around about models. Out the door before dawn, every day. And where does he go?

  • The model marketplace — new listings, delistings, price changes;
  • The benchmark boards — scores, arena rankings;
  • The popularity charts — buzz, usage rankings;
  • The open-source crowd — new releases, trending repos, repository chatter.

He comes home with a few hundred items a day. Then he goes to find Lily, buried in her paperwork.

"Lily, new batch's here. Take your time..."

"Lily, still at it? Want me to make you some coffee?"

"Lily, take a break, you're working yourself into wrinkles... ow — ow — help! I'm going, I'm going..."

Inside and Outside

The newsroom and its staff were all in place. But making it actually run took some sorting out.

The charter and the records were already kept separate, so they no longer interfered with each other.

But the charter itself was new and still being rewritten daily — Mini, Lily and Ruan bickered over it from morning till night.

So the settled part (the main branch) and the working draft (the dev branch) were kept apart.
Only what the three of them had argued into agreement went into the official charter.

And the publishing split too.
The official edition came from main; the preview of the working draft came from dev, for internal use only.

I thought that was that. Then it went wrong.

The official edition went out — with our internal discussion in it.
There was even this:

"RUAN!!! Did you take the scarf off my desk?! If it's not back within the hour, you're dead!"

Well, well. The official bulletin was full of Mini's complaints, Lily's doodles, and even a private note from Ruan to Lily.

What a mess. What on earth happened?

It turned out that both editions had been written into the same set of records (site/content/).
The records are tracked in the bookcase, so they follow the branch: switch branches and the tracked files come along, commit on dev and merge, and the changes land on main. Anything never entered in the ledger isn't tracked at all — it simply sits in the folder, whichever branch you're on. One careless moment, and the doodles and notes went out in the official edition.

So the records were split into two sets, on separate shelves. But there was still a problem — the shelves were separate; the bookcase was still one (the same git worktree).

In that bookcase, the master copy follows the branch: one git checkout and the whole master shelf changes.
But the internal discussion was never entered in the ledger, so it stayed exactly where it was. Every so often, reaching for the master copy, you grab the wrong thing.

As long as they share one bookcase, a hand can reach across the shelf to the next one — a system that relies on remembering not to grab the wrong file isn't a system at all.

So the bookcase itself was split in two — two worktrees. One holds the master copy and nothing else, and the daily publishing run reads only from that one. The other holds the working draft. That was the end of the mixing.

The Rent Bill

The newsroom had been open only a few days, everyone working away, when a demand for rent arrived.

I was baffled. Cloudflare's premises are free, GitHub's bookcase is free — where does rent come from?

Then I looked more closely. The bookcase came with a meter, and I'd run over the free allowance: GitHub Actions gives you 2,000 minutes a month, which is really rather generous...
Except that I'd only just started. The charter was being rewritten daily, the bulletin drafted over and over, and every run — build the site, generate the audio — took twenty or thirty minutes. Some days I burned through a dozen runs. Two thousand minutes didn't last long.

I called Mini in for a chat. Writing the daily, generating the audio — none of that had to happen at the bookcase. Do it at your own desk, bring the finished copy to the bookcase.
That way, GitHub Actions is only used for publishing the edition (building and deploying the site), a minute or two at a time. The free allowance is more than enough.

Perfect.

The Staff Down Tools

A daily means the bulletin goes out first thing every morning.

I'd stroll over to take a look.

And every few days I'd find the noticeboard hadn't been updated, or the bulletin was missing this or that...
Every time, I'd see red, storm in and demand an explanation from the three of them...
And every time they'd be full of grievances:

"The model calls are unstable...
We all depend on the big models, don't we... when a model has a funny turn, we can't work...
Like the other day, when OpenCode's plan changed its API and broke everything — there was nothing we could do but lie down and wait";

"And Microsoft's TTS service was upgraded, so Mini's audio wouldn't come out and the bulletin had no voice — that's not our fault either..."

Blah blah...

There was some buck-passing in it, but unstable model calls and output really are a problem.
Fine. The charter gets retry logic and automatic model failover, with three models in reserve. Next time, no more excuses.

The Fire Chief

Then again, plenty of problems can't be solved by switching models or a simple retry.
A build or a publish can fail because of a network hiccup, or a provider changing its rules, or — more often than not — the three of them slacking off and making a mess.

When something goes wrong, someone has to deal with it.

Someone has to keep an eye on things. When the publishing hour comes round, go and look: is the bulletin out? Is it right?
If something's wrong, call someone in to fix it.

And who to call? Certainly not me... I can't be bothered.

The job went to Nano (yes, the Hermes shrimp). She patrols on a schedule and cleans up the mess.
Publishing has a charter, and every step is logged. Nano reads the log, skips what's already done, fixes and replaces only the part that failed, then sends the bulletin out.
Nano is sharp; patching things up is second nature. And if she really can't solve something, she lets me know.

The Noticeboard

This newsroom has been putting out a bilingual bulletin, audio and all, every day since early August. That's several months now.

In the beginning it was chaos — the newsroom in an uproar, Nano forever firefighting and grumbling about it. These days it's calm. It's been a twisting road.

Mini, Lily, Ruan, Nano and I — dropping by the newsroom now and then for a look — have all become old friends.

The place still rings now and then with Mini's cadenced newsreader voice, Lily's scolding, Ruan's smug chuckle or his yelp of pain...

Outside the newsroom wall, the noticeboard stands quietly, day after day, showing the day's AI news and the model rankings. Unmoved by praise or neglect.

Perhaps one day a passer-by will stop, glance at it, and smile in recognition.
Or perhaps no one will ever stop at all — which is its own kind of peace.

It makes no difference. Joy alone, joy shared — either way, joy.

P.S. The noticeboard: https://techub.minixspace.com

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.