Frigga Blogs

A database gets slow. Not down, just slow enough that queries start timing out. The service in front of it retries. So does the service in front of that one. And the client. Nobody coordinated this, they are all just doing the sensible thing, whic…

There is a gap in incident response that gets almost no attention, and it sits in an awkward place. It is not detection. Monitoring is good now. It is not diagnosis either, which is where most of the recent effort has gone and where it has genuinely…

There is a version of this conversation that happens in almost every startup at a predictable moment. Production breaks in the middle of the night. The team scrambles to figure out who is responsible, who should be contacted, and what the recovery pro…

It rarely announces itself. There is no dramatic conversation, no ultimatum, no visible breaking point. What I tend to observe is quieter than that. The senior engineer who stops volunteering opinions in postmortems. The person who used to push back o…

Production went down at 11:02pm on a Thursday. The alert fired correctly. It went to Slack, as configured. The first person to notice something was wrong was a customer, who sent a support ticket at 11:43pm. The engineer saw the Slack notification at …