Skip to main content
Hat Boy Software

These articles come from audits and incidents on production estates: health probes that reported healthy while the backend was broken, two SQL Server incidents where nothing crashed, a disaster-recovery workaround that never merged, a logging setting that more than quadrupled an AWS bill, a CI watchdog running on the pool it watched, what breaks when a GitHub repo moves, redirects at Azure Front Door, and cookie-free analytics and what they cost. Client names are withheld unless the client agreed to be named.

For the engineering behind the notes, see Platform Reliability & FinOps.

13 articles

Platform Reliability & FinOps

Upgrading Hugo from 0.105 to 0.167: what broke

How we moved a Hugo site across 62 minor versions: the trial build, one hard error, three deprecations, two silent breaks, and the URL diff.

Platform Reliability & FinOps

From a shared article to a CRM lead, without cookies

How every lead from our contact form now says which channel and articles brought it, and how a nightly job puts per-article lead counts in Omnisnia CRM.

Platform Reliability & FinOps

Your load balancer health probe may be lying

Three Azure health probe failures on one production estate, and what a probe should check so that it can tell a healthy backend from a broken one.

Platform Reliability & FinOps

Azure Front Door redirect gotchas for SEO

What we learned moving our site's redirects and cache headers into Azure Front Door Standard rules: status codes, rule order, path matching and limits.

Platform Reliability & FinOps

Your CI watchdog can't live on the pool it watches

A self-hosted runner pool was down for 6 hours 38 minutes. Its watchdog ran on the same pool. What went wrong, and how to monitor CI from outside.

Platform Reliability & FinOps

What breaks when you move a GitHub repo

Moving repositories between GitHub organizations without breaking CI/CD: the hidden dependencies, and the order to change them in.

Platform Reliability & FinOps

Two SQL Server incidents where nothing crashed

Two SQL Server on Azure VM incidents where the engine never stopped: a backup retry storm, and log backups that quietly ended for seven databases.

← All articles