Writing & build logs.
Essays on software development, web builds, and AI tooling. Plus build notes from what I'm actually working on right now.
The process changed. The docs didn’t. The fix was a folder.
Three times in the captainrandom repo, documentation drifted from actual practice. Each time the fix was the same: a dedicated folder with its own PRD, roadmap entry, and devlog trail — not a patch, but enclosure.
The back-nav went to Accounts. It should have gone to the calendar.
Weeks of Accounts build work passed SwiftUI preview on every check. The first hands-on device install found gaps the simulator had never reported. Round two found a navigation bug — Back from Day view landed in Accounts, not the calendar — that the simulator had never seen.
The spring panorama has winter underneath it: audio-driven temporal layering
Two panoramas, identical dimensions, stacked front-to-back. The spring layer carries a radial cutout whose radius is driven by bass amplitude. When bass hits, winter shows through. The background is not a backdrop — it is a temporal device indexed to audio rather than time.
The ultracode audit was clean. Google still hadn't found the pages. The fix was six in-body links.
Five legal pages and /stamp-duty-calculator were returning HTTP 200, index/follow, self-canonical — and still showing 'URL is unknown to Google' in Search Console. A multi-agent ultracode review ruled out every technical blocker. The answer was the link graph: footer-only pages don't get crawled.
Three words and an arrow: the learning spec's highest-value navigability fix
Seven phases of navigation work shipped across the learning hub. The spec rated P5 — a row of prerequisite chips at the chapter head — highest-value for navigability. It was the only phase designed to answer a question the reader didn’t know they had.