Valentino Stoll
speaker
350 appearances
6 recordings
1 series
first heard Sep 2024
last heard Oct 2024
Valentino Stoll’s voice in public audio — every appearance, attributed to the second.
Trend
recordings per month · last 12 monthsNo recordings in the last 12 months.Older appearances are listed below; set an alert to hear about the next one.
Appearances
Yeah, it's funny you mentioned Datadog. We've had Ivo on before from Datadog to talk about a lot of the, like, I think memory profiling. He works on a lot of granular Ruby performance tooling, really interesting stuff. But yeah, I mean, I would love to see maybe some more, I don't know, higher level examples of like making use of open telemetry in the Ruby space in general.
Because I think that level, I mean, especially with all of the solid queue or solid trifecta or whatever stuff that's coming around, it would be nice to see something like tracing specifically introduced to Rails that would make more sense in that ecosystem. Yeah. I mean, where do you where do you start profiling stuff is like kind of like an intro to tracing. Yeah.
Like if you wanted to see like the request, it reminds me of was a rack mini profiler tool. Right. Where you you can just see a little tiny tab that says, oh, it took this number of seconds to load. this particular page you wanted to get. And you can click on and expand and see, oh, well, what did your application do at each step of the way and see how long each thing took, right?
And I think of that as like a trace a lot of the times, right? Yeah. And it's very like useful, like even when you're just starting out to see that. Right. And it helps you visualize that.
And so I feel like maybe that's what's missing is a lot of like visualization aspects of all this tracing stuff, because there's something that you look at or find useful when you're starting to dig into like structuring the traces and things like that.
you know, the new rails, like, you know, logger. where you could tag, you know, the tag logger was kind of like a start to kind of this idea of, okay, capture all of these pieces with this tag. And it's like almost a pseudo trace, I call it. But it does go along that formatting aspect of like, okay, format all the things like this in a specific way.
And I agree that there's definitely a lot to unwind there. Uh, we'll have to have you on more, uh, if you, you know, when you, uh, you know, put this together as a gem or something, cause, uh, I would love to dig into that. Um, I love the idea of the domain objects and extracting those out into a formattable way that you can then trace and follow through.
That design decision is definitely missed a lot. Seeing things like Packwork as an example was a great step in the right direction, I thought. I'd like to see more of that evolve in the Rails ecosystem of abstracting the domains into their own kind of segments and then being able to format them for traceability and things like that. I think you're onto the right. You're onto a lot here.
Yeah, I mean, that's definitely one thing that I look for when I'm looking for, you know, installing dependencies, right?
Like does the gem have its own, you know, base error class that it then can, you know, give metadata about whatever that it's raising the errors about, like more than just like a string of some error that then you have to figure out what it is like having that extra metadata that you could just, cause you can, you can just add attributes to a class, right.
And say, this error has these attributes, like it, it has meaning associated with the error. I think more people doing that is definitely going to be making that easier to do, first of all. But yeah, and then also getting more people to take on that convention. I completely agree with you there. Yeah, I mean, we are getting at time here.
Is there any last pieces you wanted to quickly highlight or mention before we move into picks?
That's awesome. Yeah, I also echo that sentiment of, you know, tooling is so important. And, you know, OpenTracing definitely is a great, great framework. And if we can improve that in the Ruby space, that'll definitely, uh, we'll, we'll be reaping the rewards as well. Uh, so let's move into picks. Uh, John, do you have anything that you want to, uh, share first or you want me to go?
Yeah, thanks. I'll definitely be digging into some of those. Yeah, I was in New York City the other day for the Ruby AI happy hour that they've been doing every couple months. This time they did demos, and I demoed this real-time podcast demo
buddy that i've made uh it's called podcast buddy uh and it just kind of like listens in the background and in real time like keeps track of the topics and the discussions and some example questions uh worth mentioning or maybe some you know topics to transition to uh and it's a lot of fun i just did it for fun but i recently refactored it uh to use the async framework
and shout out to samuel williams just phenomenal like so well put together uh the documentation is coming along it is uh lacking in some areas but i was able to just completely refactor the code so that it works with async and runs things uh you know as they come in uh and it's streaming the the whisper you know transcripts uh it performs actions in the background just
like in the same thread, all managed with async. Just, I love it. So check out podcast buddy and check out async. You can't go wrong. Async WebSocket. Now you can handle even WebSockets asynchronously, just like completely seamless HTTP two and one compatible. Love it. So check those out.
And John, if people want to reach out to you on the web or just in general, how can they how can they reach you?
Awesome. I love it. Keep up the great work and keep growing. you know, shouting from the mountaintop about observability, pulling those pillars down and just focusing on the important stuff, right? I love it. So until next time, everybody, I'm Valentino. Thanks, John, for coming on and I look forward to next time.
Awesome.
Showing 41–60 of 350 · page 3 of 18
← Previous
Next →