Frigga Blogs

Almost every incident begins with the same question: what changed? In a lot of organisations the honest answer is that nobody is quite sure, because the change was not a code deploy but a manual tweak, and those leave a much fainter trail. C…

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…

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…

Kubernetes' built-in Deployment has exactly one automated deployment strategy, the rolling update, and it is far less careful than most teams assume. It replaces old pods with new ones a few at a time, but the moment a new pod passes its…

No serious team merges application code without a review, a record of who changed what, and a way to undo it. Then those same teams build their entire cloud, the servers, databases, networks, and permissions that the code runs on, by clickin…

Ask a team how they roll back and many will say they re-run the pipeline on the previous commit. That is not a rollback. Even with identical source code, a rebuild can produce a different artefact, because dependencies, base images, and buil…