477: Change Management

Auto scaling is a simple concept. Automatically add resources when needed and automatically shut them down to avoid paying for excess capacity. How hard could that be? If you've set up auto scaling yourself, you know it's not that easy, especially using the native auto scalers on platforms like AWS and Heroku. That's why you need Judo Scale. Judo Scale is auto scaling as a service, and they make auto scaling simple and easy, as it should be. You can use Judo Scale on AWS, Heroku, Render, fly.io, and more. It's free for low traffic apps and unlimited plans start at $25 per month. Autoscale on easy mode at judoscale.com. Hello, and welcome to another episode of the bike shed, a weekly podcast from your friends at Thoughtbot about developing great software. I'm Joel Kenville. And I'm Adi Slater. And together, we're here to share a bit of what we've learned along the way. So, Adi, what's new in your world? I had one of those active record queries that is just so complicated that I honestly, I enjoy those so much. The the thing that gets closest to, like, an individual single puzzle in in programming. A lot there's a lot of things that are like puzzles, but I find those just so crunchy and fun a situation to to work on. And I think my two kind of strategies or my two things that finally worked, helped here in this, situation. The first one being to step away for the night and come back fresh the next day. Fair. I spent so much time throwing different things at the problem, but never getting exactly what I needed. But at the same time, learning so much about what was and wasn't working and, like, the domain and everything of this this particular challenge. And stepping away, coming in the next morning, I got it right away. There's something about this type of problem that really lends itself to diving in really deep and then stepping away, letting your subconscious kind of chew on it for a little while. And then the next morning comes together. In this particular instance, it's a healthcare app. And so what's the most commonly complicated thing about health care? It's scheduling. I needed a a set of records where the associated patient had an upcoming appointment of a specific type. The records have the foreign key patient ID, and then patients are related to appointments through another table functioning basically as a joint table, and still needed to be able to sort inquiry on the original record. There was a query in place that had a lot going on. I think probably requirements had changed or been focused or updated a few times over the course of developing this method inquiry in question. So there was a lot to dig through as to what was kind of the intent and what was going on there in the first place. But at the end of …