Bryan Cantrill

the degree of scrutiny that you feel yourself applying may change depending on where that code came from.

It certainly does for me, and not so much at Oxide.

But when I was at Sun, there were some times I'd get a code review of like, I really need to imagine what I would have been like to write this so that I know what I'm looking for.

In other cases, you're like, well, there's some code, and there's some tests, and I'll look around.

But a lot of the thinking has probably already been done.

Yeah, well, I do that because when I'm reviewing someone who I consider a friend and I want to do them the service of helping them with their code.

But I guess we're just motivated differently, and that's fine.

Yeah, OK.

One man's nemesis, another man's friend.

There you go.

And then, David, as you're describing, you don't want to file a crap bug report.

Man, have I seen some crap bug reports where people take you on this wild ride through a core file

And you end up just nowhere.

You're like, okay, I'm following, but all of this is just blather.

You don't need an LLM to hallucinate.

We've been doing that.

Yes.

And we've seen these bug reports where you're like, okay, there's certainly a lot of information here, but you've actually not contributed.

So that same, that empathy you're talking about is so at the core of engineering full stop, irrespective of the tools we're using.

Yeah, but it's harder to write off all of humanity.