// tag
6 posts
The cost of building with an agent is the length of the conversation. So the real skill is knowing where to cut a use case into pieces. I found the cut isn't where I expected: not between backend and frontend, but wherever the work first changes a promise to the outside world.
The cloud bill for building the whole thing was basically nothing. The agent was a different story. And the surprising part isn't the total. It's where the tokens actually went. Part 6 of a series.
The site went live for its first real match. People keep asking how it's built. But the architecture was never the interesting question. How much of it I was willing to hand to an agent was. Part 5 of a series.
I gave my AI agent auto-approve on infrastructure changes. It saved me hours — right up until it destroyed my production host. The lesson isn't 'stop automating.' It's about where you put the tripwires. Part 3 of a series.
My AI agent kept fixing a bug that wasn't fixed. It wasn't a reasoning problem — it was looking at the wrong thing. Part 2 of a series on handing an agent the whole stack.
Two seasons ago I shut down a fantasy football app with 500+ users because the operational toil wasn't worth it. Last week I rebuilt it on the Oracle stack — and let an AI agent run everything. Part 1 of a series.