Solo, but not alone: working with AI as a teammate, not a tool

For about a year now, two AI products have been in active operation, both built and maintained by one person. That person is me. The reason this is possible is not that I have become twice as productive. It is that I have become a different kind of engineer.

The frame most people use for AI coding tools — “autocomplete,” “pair programmer,” “tab on steroids” — undersells what is actually happening. What is happening, when I open my coding assistant in the morning and outline a problem before I touch a file, is that I am working with a teammate. A peculiar teammate. One that does not push back unless I explicitly ask it to. One that will produce a confident, well-structured answer to the wrong question if I do not state the question carefully. One that, when I take the time to brief it as I would brief a smart engineer who just walked into the room, will reliably hand back work that is shippable.

The bottleneck for a solo builder used to be hours per day. That has not changed. What has changed is which hours are the bottleneck. The hours when I plan are now more valuable than the hours when I type. The clarity with which I describe a problem now compounds, because the tool I use to act on the description is no longer me typing — it is me reviewing.

This shift is easy to underrate. It is also why I think the “AI agents replacing engineers” framing misses. The engineers who replace engineers are the engineers who can describe their intent precisely, evaluate proposed work skeptically, and notice when a confidently-written answer is subtly off-by-one. That skill set has a name. It is called engineering. It is not new. What is new is that it is now the only skill set that matters.

I am still the one accountable for what ships. I am still the one debugging at 2 a.m. when something goes wrong. But I am no longer the one writing every function. I am the one deciding which functions to write, in what order, against which definition of done. That is a different job. It is also a job that — for the first time in software history — can be done by one person at the scope of two products.

I do not call this productivity. I call it leverage.