Create your team of agents

I moved file conversion on dimsight.com from the browser to the server. I thought the migration would take one or two weeks. It took two days, about €20 in token costs, and the help of dozens of coding agents.

Agents aren’t the problem

I found the problem while checking errors in the dimsight.com app. To ship the first version quickly, I had put all the conversion work in the user’s browser.

That had been a mistake. Conversion failed when someone uploaded a lot of files at once. The new app looked better, but uploading files in batches was harder than before.

Before the app went live, I could ask ChatGPT to change the code and move on. Now it was in production and had converted more than 100 models. Every change felt riskier. Working with agents became clumsy, so I went back to writing code by hand.

At first I thought the agents were the problem. Then I asked a more useful question: did file conversion need to happen in the browser at all? If it moved to the server, I could remove much of the complexity instead of asking agents to work around it. So I asked them how hard the migration would be.

My quick estimate was one or two weeks. Then I let the agents test it.