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.
I didn't expect to find my own resume inside an essay by someone I deeply admire. Paul Graham recently published 'The Brand Age', a piece tracing how the Swiss watch industry crossed over from the world of precision machinery to the world of luxury brands. I couldn't keep my mind on watches while reading it. My last several years kept superimposing themselves on the page.
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.
Monorepos were born from pain. Split your code across repositories and it looks clean on paper, but things that should change together start changing apart.
A while back I was talking with a developer at another company, and they suggested I drop TypeScript and move to Go or Rust. They had three reasons. It's slow and heavy.
dd.land