I don't trust AI. I didn't when I started and I don't now, and yet most of my code is written by agents, at the rate of 267 merged pull requests a week. People hear those two facts together and assume one of them is a lie. Neither is. What sits between them is a piece of machinery I have been building for months, and this post is about that machinery. Not its blueprint, which would be useless to you, but the shape of the thing and why it has to have that shape.
Niklas Gruhn's advice is don't be a meat proxy. I have spent a couple of weeks trying to work out whether I already am one.
These days, most of my code is written by AI agents. As I mentioned in my last reflection, this happens at a pace of 267 merged pull requests a week. Yet, just when I thought my engineering instincts had grown numb to delegating code, they sharpen right back up the moment we reach the database. Watching an agent connect to a production database to alter schemas and drop records feels deeply unsettling, no matter how flawlessly it performs.
It feels like yesterday we were all told to study prompt engineering. Then you were behind if you didn't know RAG. Then came the year of agents, then harnesses, then loops, and now everyone is talking about graphs — again. Every time the name changes, the crowd rushes over. I'll be honest — I've been in that crowd more than once.
dd.land