The View from the AI Frontier

In my last post, I argued that when the same agent writes the implementation and its tests, both can encode the same misunderstanding.

Our UAT [at Swamp] suite has run approx 2000 times.

Part three of a series on agents and CI, following AI Broke the Assumptions Behind CI and The Feedback Loop Is Moving Out of CI.

A follow-up to 'AI Broke the Assumptions Behind CI,' after Paul Hammant's response.

CI queues are getting longer.

Every engineer who's worked in a mature codebase already knows this principle: you can't safely refactor without tests.

If you've spent any time in the AI engineering conversation this year, you've probably noticed a pattern.

The real reason AI engineering never stands still.

I've had versions of this conversation with founders, CTOs and engineering leaders pretty much every week this year.

Engineers have been using code they didn't write for as long as software has existed.

Six months into 2026, the difference between teams using AI effectively and teams still evaluating it isn't a head start anymore.

CVE volume was already hard to keep up with before the AI boom.

Infrastructure was the first use case we looked at with swamp.

Most SRE work follows a pattern.

I've made this promise myself.

Every company has this person.

The sovereign cloud movement is no longer a policy discussion.

I've spent more than a decade building infrastructure tooling.