I BUILDRANDOMTHINGSon purpose,
in public.
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.

On air & up next
Times in UK
This weekSchedule TBC
This week's streams haven't been set yet. Subscribe and YouTube will ping you the moment one goes live.
What's new
What I build,
and what gets solved
when I do.
AGENTIC AI & ARCHITECTURE
Building when code generation is free. How I architect agentic-first systems, what works in practice, what doesn't.
01RETAIL & HOSPITALITY OPS
23 years in operations and leadership across UK retail and hospitality. Real workflows, real failure points, real software-meets-floor knowledge.
02AI TOOL EVALS
Honest, practical assessments of the tools I'm experimenting and shipping with. Includes what didn't work.
03CREATIVE AI
AI music workflows, generative art, and video — for work and for play. Real output, shared as it's made.
04BUILD IN PUBLIC
Projects from idea to implementation. The process is the point — failures included. Shared live, in public.
05LEARNING LOG
What I'm currently studying and learning, and whether it was worth the time.
06Recent writing.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Workshop.
Build log.
In your inbox.
What shipped, what broke, what worked. No marketing. No sponsorships. Sent when there's something worth sending.



