Adam Leventhal

Because I just want to like see how it does basically on this stuff.

And I had some like, some relatively straightforward scalability work that needed to be done, a lot that needed to be broken up.

I knew how I wanted to do it.

It was going to be a little bit tedious, but I was just kind of curious to see how it did.

Yes, absolutely.

There's actually, like what needs to be done here is really quite straightforward and I can describe it pretty completely to Cloud Code.

And I'll drop a link to the actual bug itself.

Lumos 17.8.16.

So I'll drop a link in for that.

And so you can see exactly what the problem was at hand.

pretty straightforward.

Now, I was gonna use, like very deliberately, not using it, I'm definitely not closing the loop, not vibe coding it, not one-shotting it, but really, because in particular, like I am not, I'm not even gonna let it build anything, right?

I'm gonna let it, we're gonna go into the source base and I just wanted to see how it did.

And it really did, like it did remarkably well.

One thing that was really interesting

And I would, but definitely not perfectly and had some subtle issues that needed to be resolved, but we got those resolved pretty quickly.

And I think I would say like it had two subtle issues, but it had also did not have a subtle issue that it could, it made a subtle discovery as well.

And the thing that was really interesting to me about it is I was unleashing it on like a pretty big source base in terms of Illumos.

And it was really interesting to watch it effectively read block comments to understand how subsystems worked.

And to understand... And so reading not just code, but also comments.