Darren Broemmer

Yeah, Darren Bramer, yep. Bramer, ah. And O-E, it's a German, German A sound. Ah, nice.

Yeah, Darren Bramer, yep. Bramer, ah. And O-E, it's a German, German A sound. Ah, nice.

absolutely yeah well first of all thanks a lot for having me on here it's great to talk with you guys so i've been engineer engineer my whole life i will admit that i discovered ruby a little bit later in my career i was a java guy for quite a while and going all the way back to 2002 i'm going to date myself here i wrote a book on java j2ee actually so there you go that there's a dated uh bit of technology a little bit

absolutely yeah well first of all thanks a lot for having me on here it's great to talk with you guys so i've been engineer engineer my whole life i will admit that i discovered ruby a little bit later in my career i was a java guy for quite a while and going all the way back to 2002 i'm going to date myself here i wrote a book on java j2ee actually so there you go that there's a dated uh bit of technology a little bit

And so I've done all types of engineering-managed teams. I decided I wanted to go back, get hands-on keyboard after doing that. Went to Amazon Web Services. Had a great time working there. Learned a whole lot. Had a lot of fun. Met a lot of great people. And then wanted to get more into kind of combine the two things I really, really enjoy. So the technology, obviously, but also communications.

And so I've done all types of engineering-managed teams. I decided I wanted to go back, get hands-on keyboard after doing that. Went to Amazon Web Services. Had a great time working there. Learned a whole lot. Had a lot of fun. Met a lot of great people. And then wanted to get more into kind of combine the two things I really, really enjoy. So the technology, obviously, but also communications.

And so now I kind of went and switched gears. I'm now the developer evangelist for... Engine Yard and we have platform as a service tools, but I get to do my two favorite things, which are play with technology and share that with people, write about it and talk about it.

And so now I kind of went and switched gears. I'm now the developer evangelist for... Engine Yard and we have platform as a service tools, but I get to do my two favorite things, which are play with technology and share that with people, write about it and talk about it.

Yeah, so I think when you're looking at decomposing your application and doing design, you know, and really there's only one reason that we really do software design, right? We do it because we're probably going to need to change our application tomorrow, whether that be to fix some bugs or to add some new features that people want.

Yeah, so I think when you're looking at decomposing your application and doing design, you know, and really there's only one reason that we really do software design, right? We do it because we're probably going to need to change our application tomorrow, whether that be to fix some bugs or to add some new features that people want.

We can't, you know, add patterns and layers of indirection everywhere. So we need to make choices. I say that because every time you add a layer of indirection, it's not free. There's a cost to it, right? We can't optimize to be able to change every aspect of the application. You know, for example, I've been on a number of projects over my career.

We can't, you know, add patterns and layers of indirection everywhere. So we need to make choices. I say that because every time you add a layer of indirection, it's not free. There's a cost to it, right? We can't optimize to be able to change every aspect of the application. You know, for example, I've been on a number of projects over my career.

You know, the team would be, well, we need to abstract this and that so that if we want to swap out the database, Later on, we can. This is maybe a little less relevant now, but I think the example still holds. And so there was effort spent into that. Now, how many of those projects ever actually swapped out databases?

You know, the team would be, well, we need to abstract this and that so that if we want to swap out the database, Later on, we can. This is maybe a little less relevant now, but I think the example still holds. And so there was effort spent into that. Now, how many of those projects ever actually swapped out databases?

I can think of maybe one that went from a relational database to a NoSQL, and they had to make broader changes anyway. So you need to think about where can I... decompose my logic into reusable bits. And when you think about the basic Rails architecture model view controller, generally speaking, you try to push that logic down in that, if you think about it as a layer cake, down as far as you can.

I can think of maybe one that went from a relational database to a NoSQL, and they had to make broader changes anyway. So you need to think about where can I... decompose my logic into reusable bits. And when you think about the basic Rails architecture model view controller, generally speaking, you try to push that logic down in that, if you think about it as a layer cake, down as far as you can.

validations you'll always need to do before you persist to the database. Yeah, put it in the model class. But it becomes very tough when you think about this. There's lots of best practices and things about where to put quote unquote business logic. And in my experience, that often ends up coming back to the service level or in Rails, the equivalent of a Rails action, a controller method.

validations you'll always need to do before you persist to the database. Yeah, put it in the model class. But it becomes very tough when you think about this. There's lots of best practices and things about where to put quote unquote business logic. And in my experience, that often ends up coming back to the service level or in Rails, the equivalent of a Rails action, a controller method.

So if I'm a... You want your code to mirror the real world as closely as possible. And I was... You mentioned earlier, I've probably given bad advice in my career in the past too. I used to be a huge enthusiast of object-oriented. And while I think it's still valuable and has its place, I think in terms of decomposition, if you want to mirror the real world, if I'm a customer, I don't think...

So if I'm a... You want your code to mirror the real world as closely as possible. And I was... You mentioned earlier, I've probably given bad advice in my career in the past too. I used to be a huge enthusiast of object-oriented. And while I think it's still valuable and has its place, I think in terms of decomposition, if you want to mirror the real world, if I'm a customer, I don't think...