460: Programer Productivity with Valerie Burzynski

Imagine the last time you had to deal with request timeouts or backed up job queues in your job environment. Take yourself there. Can you feel it? The stress, the frustration? Here's what JudoScales knows. You're either not auto scaling or your auto scaler is not doing its job because auto scaling is supposed to prevent scenarios like this. In comes JudoScales. JudoScales helps your app smoothly handle traffic spikes while dramatically lowering your hosting costs. You can use Judo Scale's free plan forever, so you've got nothing to lose. If you want to say goodbye to those painful production incidents, visit judoscale.com/bikeshed for your special gift as a bike shed listener. That's judoscale.com/bikeshed. Hello, and welcome to another episode of The Bikeshed, a weekly podcast from your friends at Thoughtbot about developing great software. I'm Joelle Kenville. And today, I'm joined by fellow Thoughtbotter, Valerie Brzezinski. Hi. Good to be on the show. And together, we're here to share a bit of what we've learned along the way. So, Valerie, what's new in your world? Client project I'm working on, been digging into how I'm working on Sidekick, so so there's a lot of concurrency and asynchronously involved in custom internal gem that I'm working on. But they're triggering certain life cycle events in the Sidekiq client middleware and the server side and client side middleware. With client side runs when you're queuing up a job, you're pushing it onto the queue. So that's when the client middleware and you can affect how the job gets queued or tell it not to queue at that point. And then the server middleware, that's when it's actually being picked off the job being potentially being executed. Like, the job's being executed at that point, so you can run additional middleware at that point. So they have some odd interactions between what they're doing with the this middleware and the sidekick batches, which is part of sidekick pro, I think it is. Otherwise, it's enterprise, but I think it's sidekick pro. They're using both. But under certain circumstances, some of the callbacks and death handlers for sidekick won't fire. Or under certain circum circumstances, they were firing, other ones weren't firing. And, yeah, it was it was fun digging into the whole middleware and the whole method chain of their processing of jobs to see, like, okay. How are all these two different pieces interacting in odd ways in the concurrency, and how do I actually fix it? So that that's one thing that's new in my world. That's really interesting. So there's middleware sort of on the en queuing side, but then also middleware on the de queuing side. Correct. Yeah. So you can kind of, like there's some method chaining happening on the en queuing side so that if you want to reroute or change certain aspects of a job or do anything on the just a it's a hook to be able to do something when you're en queuing …