Adam Leventhal

Too big.

Why bother?

Yeah, interesting.

So in this first use case, I've got a lot of just tedium that needs to be done.

And the other thing that I think is really interesting about this case is you're doing something that we do a lot, which is like, okay, I've got this problem.

I kind of want to solve it in a way that's a little more generic where my colleagues can use it and so on.

But we...

always have the tension we always on the one hand we always encourage ourselves to hey this is a good opportunity to build a new abstraction to if you think this but we're also all kind of realistic like yeah but like we can't like not ship the next release or what have you because we're kind of focused on you know and there's always that balance and to take this thing that like oh this to to reduce the amount of work involved in this by a factor of four yeah maybe the difference between doing it and not

Totally.

Yeah.

So David, I mean, you, you were, as Rain points out, like you were among the earliest adopters at Oxide.

I think you've really shown the light for a lot of us and, and, you know, showing what these things can and can't do.

Do you want to talk a little bit about your experience of kind of getting into this?

And so what kinds of things were you kind of, where were you first really beginning to use this to beyond just search or what have you really beginning to like, okay, I can actually use this to, I can pair with it as Rain was saying.

Yeah, that is wild.

And so they are, were they primarily operating on the stack backtrace or were they stack backtrace plus, was it actually walking data structures and was it actually like meaning?

Interesting.

Yeah, that is really interesting.

I want to be using them as debugging tools a lot more.

And I'm very curious about this use case.