Skip to content

AI-Augmented Development

Context Architecture Replaces Process Ceremonies

I have been writing software for thirty years. In that time I have sat through thousands of daily standups, hundreds of onboarding sessions, and more planning ceremonies than I care to count. Most of them existed for one reason: transferring context from people who had it to people who did not. The new developer needs to know how the deployment pipeline works. The team lead missed yesterday's discussion about the API change. The architect needs to understand why the data model looks the way it does before approving the next feature.

These are not bad reasons to meet. But they are expensive reasons. And increasingly, they are avoidable ones.

Autonomy at Scale

Over the years I've tried a lot of organisational models. Standups. Retrospectives. Timesheets. Sprint planning. The full suite.

At eXOReaction, we've converged on something different. It's not a framework with a name. It's more a set of positions — things we've decided, and held to, even when they make people uncomfortable.

Mastering Deadlines: The 80/50 Rule

In 2017 I wrote a short piece out of frustration — a street-smart survival guide for developers tired of missing deadlines despite giving themselves plenty of time. Eight years later the problem hasn't changed. If anything it's worse: we have more tools, more planning methods, more retrospectives, and we still end up in last-minute panic on projects we thought we had under control.

I revisited the original piece in November 2025 with a bit of help from AI — research, narration, the lot. Here's the framework, written out properly.

Mapping Human Potential

Frøya describes herself as a cartographer of potential — not as the QA manager she was built to be.

The distinction is instructive. A QA manager checks definitions against standards. A cartographer is always working at the edge of the known, building the map as the territory reveals itself.

Frøya: A Digital Co-Worker

The question we kept coming back to when building Frøya was: what's the difference between an AI tool and an AI team member?

A tool executes tasks. A team member has a perspective, a purpose, a way of engaging with the work that adds something beyond the task itself. The distinction sounds philosophical. In practice it shapes everything about how you design, deploy, and work with the agent.