David Crespo

The two months ago being several years ago, especially in the really complicated one was that, you know, something was it was a mutex lock that was like not being taken at the right time.

And so there was like a conflict in.

And so, you know, reasoning about that was pretty tough for me, not understanding how the code worked.

But it was pretty impressive that the model was able to see it, you know, like this is where you should have taken a lock and you didn't.

It's worth looking at Ngozi specifically.

They have a quite clear LLM disclosure policy.

So Mitchell has been pretty open that he uses LLM's tooling, but they really want upfront disclosure.

So they made it easy by telling me exactly what to do.

I was more worried about sort of the embarrassment if my issue was fake for me to be like one of those guys posting issues that are fake that the LLM told them, you know, was a bug.

Yeah, well, I thought this was such a clear-cut case where it was obviously not my expertise that was operative here because I didn't have any.

You know, I had, like, there was a high level, like, I could tell that it felt legitimate.

And I think there may have been one or two things where it came up with something that I was like, that doesn't sound real.

But, you know, the amount of guidance that I actually provided in the process was a very small proportion of what actually took place.

That was what I think felt legitimate.

unsettling about it.

And, you know, the guidance that I did provide also didn't feel, you know, that ineffable human taste that people love to attribute to themselves.

It really wasn't that.

It was like finding the rust port of the stack trace, you know, symbolicate or whatever.

Well, if it had turned out to be fake, I wouldn't have been.

If my diagnosis was wrong, then that was just creating work for them.