Frigga Blogs

A reviewer opens a pull request and sees what changed. Files, lines, additions in green. What they cannot see is what happens next. Which services call this. Whether a mobile client parses that field strictly. Whether an overnight batch job reads the …

Ask an embedding-based system which code relates to PaymentService and you will get back things that look like PaymentService . Other payment classes. Functions with payment in the name. A test file. Possibly a payment integration in a completely dif…

A bug came in on something I'd written. My name on the commit, my PR, merged and running for months. I opened the file and had no idea how it worked. Not a vague memory that needed refreshing. Genuinely blank. I'd reviewed that code, I'…

Somebody asks how order creation works. You open the order service and start reading. POST /orders → OrderController.create() → OrderService.submit() → orders table → publish("order.created") And that's where the trail stops. Not bec…

There is a well-worn rule of continuous integration: if the pipeline takes longer than ten minutes, it stops being a feedback loop and starts being an interruption. When pull-request checks run past fifteen minutes, developers context-switch…

The promise of a staging environment is simple and appealing: it is a near-copy of production, so if your change works there, you can be confident it will work in production ( All Quiet, 2026 ). That confidence is the problem, because stagin…

Most teams can recite the four DORA metrics and could not tell you their own. The usual reasons are that measuring them sounds like a project, or that it means buying a platform. Neither is true if you deploy through GitHub, because the data…

Somewhere in your repository is a feature branch that was created two weeks ago, sits dozens of commits behind main, and that nobody wants to review. That branch is not progress. It is a merge you have been deferring, and it gets more expens…