Authority topics

AI software delivery

Faster generation only becomes delivery when coordination, review, ownership, and correction loops absorb the increased output.

Writing about agent-assisted delivery systems, multi-agent coordination, code review, software factories, project execution, and the operating models that turn generated work into accepted outcomes.

Core writing

Further writing

Recent analysis

Short pieces

PostAugust 20, 2026

One task in my workflow can be researched in ChatGPT, implemented by Codex, challenged by Claude, and updated through MCP.

Most project tools still assume every participant is human, which leaves someone acting as the relay between chats, repositories, decisions and the board.

Building
1 min
PostAugust 13, 2026

Every engineer knows Amdahl's law. Almost nobody applies it to AI forecasts.

A 10x improvement in one operation produces almost nothing at the system level if that operation was not the constraint — which explains both failed pilots and outsized wins.

AI transformation
1 min
PostAugust 11, 2026

A generated patch is a hypothesis until someone re-runs the exploit.

Across 6,080 AI-generated patches only 26% were clean — and a plausible-but-wrong fix direction in the prompt cut success from two-thirds to one in six, with agents overriding their own contrary evidence.

AI engineering
1 min
PostAugust 6, 2026

Four agents cleared the backlog because none was allowed to be the hero.

Astro's issue factory separated reproduction, diagnosis, verification and implementation — the improvement came from forbidding self-verification, not from adding agents.

AI engineering
1 min
PostAugust 3, 2026

AI shortened how long it takes to build a feature — not how long it takes to learn from one.

37signals cut its cool-down along with its build time. Delivery compresses; customer absorption and operational recovery mostly do not, and the ratio between them shifts.

Engineering leadership
1 min
PostJuly 31, 2026

Every AI strategy has a shadow roadmap — the work the organization quietly stopped funding.

Mid-market app counts jumped 41% in a year while a third of AI tools moved to token-based billing, which makes the negative roadmap the honest part of any AI plan.

AI transformation
1 min
PostJuly 7, 2026

AI is getting good at reviewing code. That is exactly why the human's job in review has to move up.

An AI reviewer is good at the mechanical pass — but it misses the change that fits the diff and breaks the architecture. The reviewer's value moves up the abstraction stack, to the judgment and accountability the model structurally cannot supply. The mechanical reviewer can be automated; the one who owns the consequence cannot.

AI Engineering
1 min
PostJuly 3, 2026

The model can be available and the deployment can still fail. The last mile is an engineering problem.

Enterprise AI depends on last-mile engineering: wiring AI into real tools, permissions, data, processes, and review gates. Buying capability is easier than absorbing it. The model is a purchase; the working system is a build.

AI Transformation
1 min
PostJuly 2, 2026

If an AI output is hard to evaluate, the problem may not be the eval. It may be the product boundary.

Good AI products make verification cheaper — decompose work into reviewable units, attach evidence, make the boundary between decided and inferred visible. Output that cannot be verified cheaply gets trusted blindly or ignored, and both are failures.

AI Engineering
1 min
PostJune 26, 2026

The important part of Claude Tag is not that Claude joined Slack. It is that execution is moving into the collaboration layer.

When agents enter the place where teams discuss work, the operating risk shifts from prompting to delegation, context, permission, and ownership. AI adoption becomes workflow design, not chat integration.

AI Transformation
1 min
PostJune 24, 2026

Prompt engineering was the visible phase. Loop engineering is where AI starts becoming operating infrastructure.

A loop has a goal, context, a way to act, a way to evaluate, and a rule for what happens next. The hard part is not making it run — it is deciding what the loop is allowed to optimize and where it must stop.

AI Engineering
1 min
PostJune 23, 2026

For years an app was a screen you tapped through. It is quietly becoming a set of functions an agent can call without ever opening it.

With Android 17 AppFunctions, an app exposes its actions as callable tools and the screen becomes optional. When a machine can call your product directly, your permission model stops being plumbing — it becomes the product.

Product Engineering
2 min

Built from this thinking