Dan Shipper

And the workflow that he invented is, I think, incredible.

So I should have done that, but I didn't.

And so what started to happen was we would start to have problems, and I'd be like, okay, here's the bug.

And it would go off and research it and then fix it.

But the fix was always a sort of duct tape thing.

because it didn't want to go like solve the like really deep underlying thing because the site was going down and whatever and it maybe sounds like what a human would do exactly and it depends on the human but yes uh something that's really what i would do um um

And so basically like that just kept happening.

And so it kept duct taping and putting little guards and checks and like all this stuff here.

And as a site started to go down, the complexity started to go up and each fix like would kind of fix it, but then kind of make it worse.

And

I had a couple of experts look at this over the last couple of weeks because one of the fun things about doing this stuff so publicly is when you tweet and you're like, hey, my thing is down.

People who have a lot of experience with YGS come out of the woodwork and be like, hey, I could take a look.

And what's really cool is because I sent them the repo and then ducked because I was just like, this is terrible.

Yeah.

Yeah.

Like I was like, I'm so sorry for this.

What's really interesting is they're all like, yeah, this is actually very reasonable.

It lacks some amount of coherence.

So you can you can see that the agent was like solving local problems in a particular way, but then not zooming out and being like.

well, I solve it like this over here and like this over here, and those should match so I can understand the whole thing.