Adam Leventhal

You say in your, this, these issues that you're like, I, I, but it's also like, what do I do?

Like this thing crashed.

Like I, am I just supposed to like not give someone the feedback that this thing has crashed?

And I've got like, or am I supposed to just like sling an issue in there with, I mean, it's like, it just feels like you're being actually helpful to the project.

Right.

It was okay.

So I think it goes to, and, you know, we've talked a bit about RFD 536, where we kind of talk about our own LLM thinking at Oxide, and it just goes to that, like, having empathy for the person that's going to read this and making sure that, in this case, really contextualizing it.

But also, like, it sounds like you're doing your own checking to make sure that the degree that you can, so...

And then on that, like for my, you're exactly right.

And like, I mean, oh, look, I'm just ashamed to say it, but I'm gonna say it.

Like the way I would review code from like a nemesis, you know, a nemesis integrates code and you're like, I am gonna, I'm gonna get my name.

And I'm like, one of the things I realized I needed to do was for my own self-review and for reviewing people that were not my nemesis, I needed to channel that dark part of my brain that's like, I'm going to find this thing in here.

And that's like, I mean, it's embarrassing to say, but it's definitely true.

It feels like you're just trying to explain away a whole bunch of the code review comments.

Very good code review comments.

I mean, it feels like comments you'd give a nemesis.

That's right.

OK.

Yeah, that's a very good point.

Yeah, but to Adam's point, I don't like that when you get bogus bug reports without LLMs either.