ONLINE · OPEN FOR FREELANCE BUILDS// BUILDING IN PUBLIC
$ whoami → captain-random

I BUILDRANDOMTHINGS

YEARS WEB DEV
20+yrs
YEARS IN RETAIL
23yrs
POSTS PUBLISHED
257articles
RECENT COMMITS
270/30d

Hey — this is Captain Random. I build production software and experiment with how far I can push my imagination into the digital realm, bridging the gap between technology and the problems worth solving. This site is for everyone — here you can see real projects, real workflows, and honest evaluations of the tools I use and build. It's a new project, and it'll grow with every commit. Stick around and watch it take shape.

Live hub

On air & up next

Sat 7 Nov · 22:35 UK
Times in UK
Captain Random with headset and controller beside an on-air lampThis week

Schedule TBC

This week's streams haven't been set yet. Subscribe and YouTube will ping you the moment one goes live.

Usually evenings, UK time
This week live
Mon2TBCTo be confirmed—
Tue3TBCTo be confirmed—
Wed4TBCTo be confirmed—
Thu5TBCTo be confirmed—
Fri6TBCTo be confirmed—
Sat7TBCTo be confirmed—
Sun8TBCTo be confirmed—

Recent writing.

Essays, notes & build logs
Build Logbb finance
#01
2026-11-075 min read

Name the account at the other end: how money features ship in an iOS budget app

Four incidents from an iOS budget app's money layer, each resolved by the same reflex: check the layer that is actually broken, name what the app knows, and let the UI admit what it does not. A misread disconnection, a transfer with one side missing, an unlink that deleted, and a currency question that could only have one right answer.

Read post→
Build LogiOS
#02
2026-11-076 min read

Three 'bank disconnected' bugs in five weeks — the message was wrong every time

A cascade delete, a gitignored config file, and a tailnet route pointing nowhere: three failures that all surfaced as the same disconnect screen. Diagnosing each one meant ignoring the error message and working down the stack.

Read post→
Build LogiOS
#03
2026-11-064 min read

Four connection failures that had nothing to do with the connection

Halifax pending missing, four accounts unreachable, a build that arrived without its config, then a disconnection report that turned out to be false. Each symptom said the same thing. The actual cause was always something else.

Read post→
Build LogDevOps
#04
2026-11-065 min read

I MD5-checked the server. The files were right. The browser hadn't noticed.

PR #566 landed six new category icons on the cPanel host, byte-identical to the repo. The browser ignored them: a year-long default Cache-Control header meant the June originals were locked in until the URL changed. The captain_random deploy pipeline now versions every asset URL on update.

Read post→
Build LogPerformance
#05
2026-11-015 min read

Better images land on the server. The browser may still show the old ones.

Regenerating site images is the easy part. On a static cPanel host the browser might still serve June's render in November, and the LCP image — even when marked priority — won't get fetchpriority if your export bypasses Next.js's optimiser. Two separate failure modes, both invisible until you look for them.

Read post→
Build LogDevOps
#06
2026-10-315 min read

I replaced six icons. cPanel had cached the old ones for a year.

I merged the new category icons, deployed, and checked the live site on my phone. June icons, still. The server had the new files — md5 confirmed it byte-for-byte. cPanel serves /icons/ with a one-year immutable cache by default. Image work isn't done until the URL has changed.

Read post→
Build LogJavaScript
#07
2026-10-276 min read

Two bugs, two green builds: the JS escape that isn't, and the clock that crashes Safari

Both bugs had passing tests and green CI. The semicolon escape was caught by re-reading the output file before merge. The WebKit clock crash shipped and surfaced on iOS. Neither was a logic error — both were assumption errors the test suite shared with the implementation.

Read post→
Build LogStreams
#08
2026-10-266 min read

The /streams/ page compiled clean. The audit found five bugs.

The /streams/ schedule page compiled clean, rendered correctly in dev, and had five bugs. Midnight week-crossings, DST ambiguity, spring gaps, ICS escaping failures, and a live card that didn't know when a stream ended — none surfaced until an independent three-agent audit ran before PR.

Read post→
TestingPython
#09
2026-09-256 min read

post_today opens two connections. The test fixture only controlled one.

Three tests in test_post.py broke when auto_mode was turned back on in production. No code had regressed. post_today also opens its own connection to read the auto_mode flag, independent of the connection the fixture supplies, and the test hadn't controlled it.

Read post→

Build log.
In your inbox.

What shipped, what broke, what worked. No marketing. No sponsorships. Sent when there's something worth sending.

Plain-text only. Unsubscribe in one click. We store your email, the date you confirmed, and a one-way hash of your IP (for abuse triage). Nothing else. Privacy policy.

Captain Random holding out an envelope