Project-filtered dev log routes, and the concurrent session that snuck up on me
Fixing two dead-end homepage links meant building tag filtering, then a git collision from a concurrent session I didn't see coming caught me mid-ship.
Fixing two dead-end homepage links meant building tag filtering, then a git collision from a concurrent session I didn't see coming caught me mid-ship.
Chasing down why non-production branch builds never ran on Cloudflare Workers Builds - a KV namespace nobody asked for, and a trigger model I'd misread.
Astro's fallback rewrite silently shadows real translations behind getStaticPaths, and Astro.url reports the wrong page location on fallback-rendered routes.
A one-off axe run isn't a check, it's a snapshot of one moment. Porting the sibling site's pa11y-ci setup, with wrangler dev resolving bindings for free.
Star counts undersell infrastructure. I hand-wrote a subsection above the auto-generated cards, then found a tooling assumption that didn't survive checking.
A grouped 12-update dependabot bump hid a Tailwind major that broke loudly and an Astro major that broke silently, triggered by one unmerged branch.
The check that shows up on merged PRs is Cloudflare reporting a build that already ran, not a pre-merge gate - so the gate became a synchronous local build instead.
The marketing page pitched new-release tracking - an incumbent's home turf - while the view model's doc comment had the real pitch all along.
The apex domain sent no mail and had no SPF or DMARC, which meant anyone could forge it. Two DNS records, ninety seconds in a dashboard, one dig to verify.
The site-wide mobile clipping bug that didn't exist: headless Chrome silently clamps to a 500px floor and crops the screenshot to whatever width you asked for.
Page 1 of 2