
From Vibe Coding to AI Operations
The seven principles I use to turn Claude Code, Codex and scheduled automation into a governed engineering workspace.
The model is 5% of an enterprise AI project. Identity, permissions, memory, audit, cost. The other 95% decides whether it ships, and it's where the careers are going. Practitioner written from inside real deployments. Start with two free field books.
Live Last read · last published · next check

The seven principles I use to turn Claude Code, Codex and scheduled automation into a governed engineering workspace.

I’m helping a friend build a new system for his business with a Claude Code engineering team. Almost everything that matters sits outside the model.

A UAE tender assumed in-country AI inference was broadly available. The Jurisdiction Screen found a much narrower answer.

Agentic autonomy has a price when you're not sat at your desk.

Read the verbs before anybody prices the architecture.

Nobody caps a Facebook campaign that returns $1.50 on the dollar.

Each one is readable from the business case. None of them is the model you chose.

Nine months of building with a recurring requirement has changed my relationship with Claude Code.

Every BI vendor has spent eighteen months rebuilding around conversational AI.

Just because it passes functional tests doesn't mean it's financially viable