Own the Verification

Introduction

QA and verification are an integral part of how we code with AI today.

Without that process, you are vibe coding. Vibe coding is letting the model write the software and moving on because it looks right. The models have gotten better. You still have to own this as a software engineer. How your code gets verified, and how it gets pushed to production, is the work.

What if we began to treat that check as part of the engineering, not as something we hand off?

How You Own It

You can own it in two ways. On the pull request, the agent opens the actual app, uses it, and records what happened before the change passes to production. Or the agent triggers a real suite of tests and runs that suite in a sandbox.

Reduce the Dependency

If you can run these checks, and the tools that run them, with less dependence on a cloud provider, that is a great benefit. A cloud sandbox is a computer you rent so the agent can do the work somewhere else. The check does not have to live there. If you cannot run this yourself yet, the lab subscriptions are fine for right now. The direction is to depend on them less.

The T3 Code Fork

What I have started is a fork of T3 Code. T3 Code is the app. Ours is the Sircularity fork, and it runs on multiple machines, with webhook automations added on top.

An automation is a task you write once. It does not have to wait on a clock. You create it, you get a webhook URL, and you point GitHub or Basecamp at that URL. A pull request closes, or a Basecamp to-do comes in, and that delivery can go to a different connected machine. The event is filtered. If it matches, the automation starts there.

The run shows up as a thread in T3 Code. A thread is the place we watch the job and steer it if we need to. We are still experimenting. For us, this is already better in all the ways. It is our own tool for this process.

A Small Team

If you are a small indie developer, a small business, or a small team, try as much as possible not to outsource that compute. Build your own tools. Engineer the process so it is clear to you. That is how you move at light speed.