The New Backend Engineering Lead at TextUs - Brittany Martin


By corner of the world is very different and so I think I've kind of alluded to it on some of the episodes we've recorded up to this one but nick, you are my very favorite co host. So of course, I waited until you were back on the podcast so that we could discuss all the changes but I have recently shifted roles. So I quietly changed my linked in quietly changed my twitter and my get hub but I am the new engineering lead for the back end at text us. Congratulations that is that is huge right I don't even know where to begin but. I guess the best place is at the beginning. So how long ago? Did you kind of find your way into the world of Texas yeah. So ask the listeners know I've been at the trust for about five years, which was fantastic because I leveled up. So much of the trust, a lot of my conference talks that I gave came from the work that. I was doing at the trust I loved those working at a nonprofit affecting the arts and the Pittsburgh community because when I came back from San Francisco, I really wanted to get re-involved with Pittsburgh and there was no better place to do it with the trust being a small nonprofit and you know there was only so many places that I could grow up words. I decided to start considering my options, and so I came across Texas and text. US. Basically is a business class text messaging software and they're built in rails, which of course, is very important to me as the host of this show to continue working on ruby on rails. So you know I have bet my career on it. And the Texas currently serves the ASS staffing recruiting industries mainly though they also serve a lot of different industries but it's a really interesting and complex code base and they use a lot of the dry principles, which is that I was somewhat familiar with, but I hadn't worked one on one with. So how about you neck? Have you used a lot of dry rb? So when you dry principles, do you mean like actually using like dry rb and the dry rb tooling and the ghost? Yes heavily on my goodness. So I have literally just wandered so far as hearing about it in a podcast or you know and I and I, think I follow the maintainers on twitter and reading about five never crossed that threshold to actually using it even in a in a toy up. So House have been. kind of seeing that world is imagine it's quite interesting. Yeah. I'm coming off of a code base where we used a lot of service objects. So in some ways, there are some principles there that are somewhat familiar where you don't stack all of your logic into your models and controllers, but dry principles. It's just it's very clean and I'll tell you that during the interview process with Texas, which first of all was a really fantastic. Interview Process and I hope a lot of companies have processes like this it my process probably took I would say about five weeks and that involved a lot of one on one in conversations with their product manager the CTO, their chief architect, my partner, who is the engineering lead for the front end and just really making sure that it was a good culture fit and then I ended up doing a pairing session with the chief architect and. What was neat about it is that we tackled some very rails lia problems, but then as towards the end of the interview. He gave me some examples of how my code could change to actually reflect those dry principles and how that is how they manage the code in code base and I left that interview just ceiling. So intrigued about how I feel that I knew ruby on rails fairly well, but just seeing it in that sense it got me really curious and I was like this is this is. going. To. Be Great for my career. It must be amazing to get another set of eyes because I have to commend you you know. There's A. Strong trend in tech where people you don't hear the five years that often anymore. I don't think you you see is short as eighteen months to I'd say, even three years I'd look at unlinked and say, wow, that was a while. So so it's definitely you know there's all the. Normal aspects of changing changing a job but I think from a code aspect just saying these different ideas you know and. It's like a super learning experience all over again if you're around a bunch of intelligent people working in this code base and and especially with tooling that you may not have used before so must be. An absolute thrill.

Coming up next