466: All about keynotes with Aji Slater

Have you ever set up auto scaling on your production app? Maybe you know how painful it is to use built in auto scalers on platforms like AWS and Heroku, the confusing settings, unreliable metrics, and no clear visualization of what's really happening. Judo scale is the auto scaler built to make your life easier. With smart defaults and beautiful charts, you'll be auto scaling in minutes. The result, a much lower hosting bill and a bulletproof prod environment that easily handles traffic spikes. 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 today, I'm joined by fellow Thoughtbotter, Aji Slater. Hey there, cats and kittens. And together, we're here to share a bit of what we've learned along the way. So, Aji, what's new in your world? Well, right now, my current client has an application whose front end is in Angular. This is not a technology I've really worked before. It's got a Rails back end, so I'm pretty comfortable there. And, you know, we have to we have to learn new things all the time, find ourselves in new environments, figure our our way around. That's just kinda what we do as consultants. But because of the timing of where in the world this project is happening, it's been a fun experiment for me to try an alternate way to learn a new framework in a new environment. I've been using a lot of LLM tools to learn my way around, not necessarily the application itself, but learn my way around Angular, being able to ask it questions to explain something that might not match up exactly what's in the docs. And it's been interesting experiment. I think things have gone well as far as, like, the project is concerned, but I've come away with a a lot of learning as to how I can best interact with these new tools. How has the experience been using LLM for effectively documentation search versus a traditional Google search? It is definitely helpful in that I don't need to know what keyword I have to look for beforehand, especially in a completely new environment. You don't always know those terms. Right? And so it's been fantastic for that because I can put a line or two of code into it and be like, can you explain this to me? And, you know, give it the different libraries and packages, things that we're we're using. So it's certainly helpful for that. I have not found it to be very good generating new code for this environment. There are a couple of unique, probably not unique, but there's a combination of libraries supporting the way that this application works that is not …