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 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.
A hole in spring: the bass-masked radial portal that skipped the shader
Two panoramas at identical dimensions, one layered in front of the other. Cut a radial hole in the front layer, drive its radius with bass energy, and winter is visible through spring. No shaders, no post-processing pipeline — just winding-order arithmetic on a canvas clip path.
Bass as a window: the low end punches a hole in spring and shows you winter
Adding a winter panorama behind the spring layer did nothing until the spring canvas got a radial alpha hole driven by bass frequency. The moment that connection landed, the low end stopped being a brightness signal and became a literal window between seasons.
Four lines in a published article leaked my macOS username to the live site
PR #17 was a four-line diff across two files. One of those lines was in the body of a published article, rendering a real macOS username in the browser. The fix was substitution — but the pattern it revealed was wider: three surfaces in the same audit window, the same failure.