David Crespo

So it hinges pretty tightly on the fact that they were legit.

Yeah, yeah.

It is really infuriating to see a bad AI bug report.

I'm probably more optimistic than most people about LLMs, and I think part of that is just working at Oxide, and I don't really see anybody doing the pathological things that we hear about online.

Everybody's so careful and serious at Oxide, so I worry that I'm biased toward optimism because I'm not seeing the median user of these tools.

But then I see one example.

I get one bug report on a repo that I'm actually familiar with.

I'm like, forget it.

Throw these out.

We're done.

I've been surprised that the tooling for maintainers hasn't been able to keep up.

I mean, you expect some lag, right?

There's the volume of garbage has to balloon for a bit before it becomes such a big problem that people are incentivized to put some work into solving it.

But I think one of the things we're going to see in the next few months is maintainers more openly using LLM tooling to cut through that problem.

more S of AI bug reports and AI.

yeah you definitely like it to be built into github pretty soon i mean there are tools like graphite code rabbit i mean that's kind of what started me on this i saw someone you know praising this this tool graphite which does look really nice um online and it's like 20 bucks a month a seat i was like wait 20 bucks a month a seat i can write that in a script so it's like so i wrote a script that pulls the diff the comments um the pr body um

And just feeds that into an LM, just says review this.

And you have downsides there where a lot of times there's additional context that's not in the diff.

Like if you're using something that is imported in the code already, the import is not in the diff.

So it's going to say, are you sure you're importing this?