Frigga Blogs

There's a category of outage that makes you doubt your monitoring. Error rate is through the roof. Requests are timing out. And every panel you open looks fine. CPU is low. Memory is low. The database is up, responding, barely working at all. …

Every other failure in production arrives unannounced. A dependency falls over, a config change does something unexpected, traffic goes somewhere nobody modelled. Certificate expiry is not like that. The date is printed on the certificate. It has be…

Ask a founder what their engineering team needs and you'll usually get an answer about outages. Faster detection. Better alerting. Something that helps when things go wrong at two in the morning. That's fair. Outages are visible, they…

Someone builds a working version over a weekend and shows it round on Monday. It does about 60% of what the tool you were going to pay for does. The room gets a little excited. Two engineers, six weeks, and you own it. That's the pitch, and the …

The hard part of joining a team isn't the code. It's that you don't know where anything is, and every question you have is one somebody else could answer in about four seconds. So you either interrupt them, or you spend forty minutes fin…

The change looked safe. Rename a field, tidy up a response, remove something nobody uses. I searched the repository I was working in. Nothing came back. Shipped it. The thing that breaks in this story is never in the repo you searched. It's in…

I assumed private repositories were the safe ones. Everyone I've asked assumed the same thing. GitGuardian's 2026 report says 32.2% of internal repositories contain at least one hardcoded secret , against about 6% of public ones. Roughly six…