Frigga Blogs

For most of the last decade, the default way teams organised their code was to cut a branch, disappear into it for a week or two, and merge it back when the feature was done. That model has quietly lost the argument. By 2025 the industry had…

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…

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…

Most teams do not have a rollback. They have a hope that they will improvise one when something breaks. The data on how that goes is stark. In the 2024 DORA State of DevOps report, elite teams restore service after a failed deployment in…