Paul Dix

You can get them into a loop and

where they'll work for hours grinding away at something, right?

Like if you have a performance optimization problem, for example, if you create a tool where you say you run this tool and these are the signals you look at, and they tell you whether or not you have improved or gotten worse,

And you give that to an agent and you just put it in a loop, it will just grind away at the problem until it either comes up with something good or it doesn't.

So at the end of a few hours or a night or whatever, you can look at it.

You can be like, okay, that's good.

And I would say the same is true for functionality.

I mean, I will say...

All of my experience is based on backend software development.

So I don't have front end software development experience in this.

I did actually over like the,

holiday period do a side quest where I had to do some front end stuff.

And that was my first opportunity to use something like Playwright MCP to have Claude go through and hit the browser and try and fix things and stuff like that.

And again, it worked insanely well.

I was shocked.

I had it porting a piece of UI code to try to make it native as some WASM app inside the database.

And again, like it did the whole thing and I'm just, but I'm not going to ship any of this code is the thing I did.

Like I have all this stuff where it's like, I feel like I can get things.

I can get a demoable prototype.

I can get what looks like working software, but I don't know how to cross over the line to get it to like something that we actually want to deliver.