Darren Broemmer

So you can use those extensions as well. So yeah, so you get benefits from containers, not just in the deployment, but I think in the development as well. And hopefully you never have to hear the phrase works on my machine again. That helps to alleviate some of those issues.

So you can use those extensions as well. So yeah, so you get benefits from containers, not just in the deployment, but I think in the development as well. And hopefully you never have to hear the phrase works on my machine again. That helps to alleviate some of those issues.

Yes, there's a whole other paradigm shift that we now have to think about, right? Well, I know a lot of the Ruby gems do work on it, but there's a handful that don't. And I know the company I work with is actually... We're investing, actually looking for Rubyists to help get all of those gems up to speed on ARM because the price improvement... Sorry, the performance...

Yes, there's a whole other paradigm shift that we now have to think about, right? Well, I know a lot of the Ruby gems do work on it, but there's a handful that don't. And I know the company I work with is actually... We're investing, actually looking for Rubyists to help get all of those gems up to speed on ARM because the price improvement... Sorry, the performance...

And price improvement is really significant. So it's a big boost.

And price improvement is really significant. So it's a big boost.

No doubt. 100% agree. Now that I'm a developer evangelist, I shifted from engineer to, I guess you could say I'm on the marketing side. So still an engineer at heart. But the phrase game changer gets overused so many times. When you go to conferences, you hear, this is a game changer. That's a game changer.

No doubt. 100% agree. Now that I'm a developer evangelist, I shifted from engineer to, I guess you could say I'm on the marketing side. So still an engineer at heart. But the phrase game changer gets overused so many times. When you go to conferences, you hear, this is a game changer. That's a game changer.

I think the use of ARM, what we're talking about here, I think actually does fall into that category. I think it's a big shift and you're going to see a lot of energy put toward that. And I think it's really going to help things out. I mean, people complain about sometimes Rails being slow. It's like, well, if you run it on a faster computer, that's a really nice way to solve that problem.

I think the use of ARM, what we're talking about here, I think actually does fall into that category. I think it's a big shift and you're going to see a lot of energy put toward that. And I think it's really going to help things out. I mean, people complain about sometimes Rails being slow. It's like, well, if you run it on a faster computer, that's a really nice way to solve that problem.

Certainly cost effective there. It's a lot cheaper than the person hours that you might spend diving into that potentially.

Certainly cost effective there. It's a lot cheaper than the person hours that you might spend diving into that potentially.

Yeah, it's a great question. So, you know, I mentioned that earlier, I wrote a book with the phrase best practices and a title. And I think I have a little bit different opinion take on that now. I believe that the use of microservices, what we've been talking about, is a great practice to do if it works for you. And it's probably, you know, it's not a one size fits all.

Yeah, it's a great question. So, you know, I mentioned that earlier, I wrote a book with the phrase best practices and a title. And I think I have a little bit different opinion take on that now. I believe that the use of microservices, what we've been talking about, is a great practice to do if it works for you. And it's probably, you know, it's not a one size fits all.

So it's more of a concept that you can apply to your situation. If it's really hard to to untangle those concerns, maybe you just keep it in that single app. Maybe it's not worth doing, not worth the effort to break it out.

So it's more of a concept that you can apply to your situation. If it's really hard to to untangle those concerns, maybe you just keep it in that single app. Maybe it's not worth doing, not worth the effort to break it out.

Yeah, that's a great example. And I think that if you've identified that as a need, it's used in more than three places, which is a good general rule for reuse. So you want to package that up and not repeat yourself across that group. So how do you deliver that capability to the other users of it or even reuse it yourself? And so...

Yeah, that's a great example. And I think that if you've identified that as a need, it's used in more than three places, which is a good general rule for reuse. So you want to package that up and not repeat yourself across that group. So how do you deliver that capability to the other users of it or even reuse it yourself? And so...

You could just point the other teams or the other developers to the repo. You could build a gem, package it that way, which is also a nice way to do it, or the route that you described. You could make it an API or a microservice, and it is. It's well-defined, and it is. That's a perfect use case for a microservice. I will say, Chuck, you also brought up the authorization.

You could just point the other teams or the other developers to the repo. You could build a gem, package it that way, which is also a nice way to do it, or the route that you described. You could make it an API or a microservice, and it is. It's well-defined, and it is. That's a perfect use case for a microservice. I will say, Chuck, you also brought up the authorization.