Blog

Practical writing on running, supervising and shipping work with AI coding agents.

slack to aislck

How to Turn a Slack Conversation Into a Ticket

Turn a Slack conversation into a ticket with repository context, acceptance criteria, ownership, and traceability that keep engineering work moving daily.

·6 min read
azure devops ticketworkflow

Azure DevOps Work Item to AI Coding Agent

Turn an Azure DevOps work item into an AI coding agent session with the context, approvals, checks, and traceability needed for production delivery now.

·7 min read
linear issue into agent sessionworkflow-continuity

How to Turn a Linear Issue Into an Agent Session

A Linear issue is rarely a complete implementation plan. How to turn one into a scoped, supervised agent session — context assembled, repository resolved, and every diff reviewed while it is still cheap to change.

·7 min read
Jira Ticketworkflow-continuity

Start an AI Coding Agent From a Jira Ticket

A ticket that says "Add SSO support" is a starting signal, not an agent-ready task. Turning a Jira item into a bounded, reviewable agent session — with a human in control at every stage.

·7 min read
build-in-public

915 Users, 11 Power Users, 4 Paying Customers

Our dashboard said we had eight paying customers. Four of them were us. What we found auditing our own analytics, and the honest version of the numbers.

·6 min read
build-in-public

110 People Started Our Trial. One Converted.

A 0.91% trial conversion is not a copy problem in disguise. So instead of rewriting the paywall, we emailed the other 109 and asked one question.

·6 min read
cost-control

What an Overnight Agent Actually Costs

The expensive part is not the code an agent writes. It is the context it re-reads — so cost grows with turns, not with lines changed.

·4 min read
troubleshooting

When Your Cloud Workspace Won't Start

An instant failure means the request was rejected before anything was built — and the HTTP status will probably not tell you why. A five-minute triage.

·4 min read
engineering

Four Layers of Wrong: Shipping SSR on Vercel

It took four deploys to server-render one page. Three of the four failures returned 200 OK — a successful status is not evidence of a working page.

·5 min read
first bugengineering

The Green Test That Defended the Bug

Two tests, both passing, both well named, both asserting the wrong behaviour. Neither was found by reading them — and coverage numbers cannot see either.

·4 min read
engineering

The Empty Catch That Cost Us Half Our Users

57.8% of users who chose a deploy target never finished. There were no error reports — the error dashboard was clean because of the bug, not despite it.

·4 min read
agent-supervision

Long-Running Agent Monitoring That Holds Context

An agent can produce a diff in ten minutes. The hard problem starts at minute 45, still tracing a bug while its owner is in transit. Monitoring is a control loop.

·6 min read
workflow-continuity

Async AI Coding Workflow That Keeps Shipping

Async agent work is not unattended delivery. It plans for the developer being away: structured context up front, visible checkpoints, and approvals backed by proof.

·7 min read
workflow-continuity

AI Workflow Continuity for Coding Agents

An agent can produce a useful diff in 20 minutes, then sit idle for six hours. The constraint is not model capability — it is continuity across people and time.

·7 min read
ai worflowagent-supervision

Remote AI Supervision for Coding Agents

Remote AI supervision is the operating layer between a stranded agent session and an unreviewed merge: see the work, keep its context, and decide from anywhere.

·7 min read
agent-supervision

How to Supervise AI Coding Agents From Anywhere

A coding agent does not stop being your responsibility because you closed your laptop. What remote supervision really requires is context and control at the moment a decision is needed.

·6 min read