Frigga Blogs

A repository is no longer where an AI coding tool's context has to end. Modern software rarely maps cleanly to one repo. A frontend may depend on backend services, shared libraries, workers, infrastructure code, and configuration spread across s…

A frontend calls an API. That API invokes another service. A queue triggers a worker somewhere else. One change can cross four repositories before the feature is complete. The problem isn't getting another coding agent. It's giving the agent…

Give an AI more code, and eventually the context itself becomes the problem. Across 10,000 files and millions of functions, there will always be something that looks relevant - another similarly named function, an outdated reference, a README menti…

On the last day of March 2026, one compromised maintainer account turned axios, one of the most widely used JavaScript libraries in the world, into a malware delivery system. The package ships roughly 100 million downloads a week and sits un…

A container image is mostly software you did not write and cannot see: base-image OS packages, transitive dependencies, and libraries pulled in three levels deep. That is fine until a critical vulnerability lands. When a Log4Shell-class flaw…

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…