Rails Business
Brendan Buckingham and Ryan Frisch talk about developing with Ruby on Rails and how to leverage it to build a business.
Rails Business
Developer Origins and Ruby on Rails Journeys
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
In this inaugural episode of the Rails Business Podcast, Ryan Frisch, CTO at Locable, and Brendan Buckingham, VP of Engineering, dive into their journeys into the world of Ruby on Rails. They discuss their initial forays into programming, transitioning from different languages like PHP to Ruby, and the allure of Rails. The episode also covers the challenges of managing tech debt in growing companies, the role of junior developers, and the importance of mentorship. Tune in for insights into their developer origins and the evolution of their careers with Ruby on Rails.
00:00 Introduction to the Rails Business Podcast
00:36 Ryan's Journey into Ruby and Rails
03:23 Brendan's Path to Rails and Ruby
06:00 Challenges and Milestones in Learning Rails
17:02 Hiring and Mentoring Junior Developers
18:05 Dealing with Tech Debt and Refactoring
23:42 Wrapping Up and Future Topics
Links:
Welcome to the rails business podcast.
Ryan:I'm Ryan Frisch. I'm the CTO at Locable and just a general Rails enthusiast.
Brendan:And I'm Brendan Buckingham we're going to start with some background. I've been doing Ruby and Rails. Since 2013, I'm the VP of engineering at a small startup I've been running the engineering team there for five years now. It's a, definitely a change from, writing code and getting to be heads down, which I know you get a lot more of that Ryan than I do these days. So interested to hear a little bit more about that at some point, probably.
Ryan:Yeah, definitely. How did you get into Ruby What, what brought you to Ruby? Was it just a job necessity or was there some other path that got you going?
Brendan:Yeah, that's a good question. I actually started with PHP and to even step back to why I got there. I was interested in programming in college, and I actually took a programming class and decided that I didn't feel like finishing the programming class, so I got an F and basically just dropped it in the middle of the semester when you couldn't drop it anymore. anyways I had an HTML course in high school, which was cool. I thought that was really neat, but I had this, I don't know, like mental block that I can't be a programmer. I'm just, whatever. Doesn't, didn't fit my perception of myself at the time. Until I was in, my first job, which was not programming at all. And then I was like, I'm going to automate all these spreadsheets. Cause this is way more fun than the actual spreadsheet work. And then it went back to, Oh, HTML was cool. Like web seems really cool. That was 2005, six, something like that. When web was still a big thing and becoming a big thing. And so I started with PHP cause my brother was doing that. And then I was hearing about rails and Ruby and it was like, that sounds way better. But. I decided to go with the hard path of I'm going to do PHP first really just get the benefit of working with Ruby and Rails. And so that's how I found it anyways, was like blog posts and whatever, DHH and those guys were doing at the time.
Ryan:I remember distinctly trying to learn programming several times, right? PHP C sharp.
Brendan:So you went way deep into the stash.
Ryan:It never clicked and it wasn't in that order. I did, C and C plus was in college, like courses. PHP came later as I got into the WordPress years. C sharp was somewhere in between there. that was just the new one, but it never clicked until I picked up rails, then it was like, wow, okay. I. I align with this way of thinking, like I can get past the details of connecting to a database and I can just build stuff and that's when it really took off for me and I'm sure we'll get into it, but there were like different, milestones that I reached on that journey. First was just get, a website running, which with rails says. You probably are aware is a lot easier than a lot of other languages. And then, you hit these ceilings, right? And it took me years to get over some of them. And I'm still, hitting my head on the, the next one. I'm sure they're, they go on, there's always a new ceiling to hit. But it sounds like we have a pretty similar background.
Brendan:Yeah. What was it about Rails that attracted you? Where'd you find Rails or Ruby?
Ryan:Yeah, great question. To answer that question, I'll give it a little bit of my origin story. and it's similar, so, I'll try to skip the similar parts. I went to RPI as a computer systems engineering major. I quickly found that did not work for me. I switched to comp sci, I did that for about a semester. and if I'm being honest, I think I was just like. Not at the right point in my life to really dive into, to computer science. So I ended up switching to it management, which had, more of the website, a lot of the product UI, UX stuff, the business and the management piece. And that's what I ended up getting my degree in. I promptly graduated and went and worked for finance for eight years. So nothing to do with programming, but in the role that I ended up there Again, similar to you. I started automating things. At the time it was VB script. That's pretty
Brendan:much
Ryan:VBA. Yeah, exactly. Yeah. VBA. That's what it was. So I quickly realized that I didn't want to be in finance. So I quit that job. I moved to Florida. I just started freelance marketing. I needed to make some money. I had that sort of background. And through that, I met my current business partner and at locable, they were already using Ruby on rails. So that was how I got introduced to it. And when I joined locable, I wasn't doing any development. I was actually doing marketing for the most part, and that morphed into customer success and support and just all the things that needed to be done as a two person company. He did sales. I pretty much did everything else and we were outsourcing our development. And I came full circle and it's you know what? I really enjoy programming. I've always wanted to be a developer. I just never, could get over that initial hump. So I started reading the rails docs. I spun up an app. Then, I took the course that I forget. I always forget the name of the course, but the course that. Michael Hartl's tutorial. Thank you. Like everyone does. And eventually I was like, you know what, I'm going to try to commit a bug fix to our app and I did, and that was the, that was the beginning of the end for me, fast forward and I don't even know what year that was, but it was probably like 20. 15, maybe so that you could say I bet was a, I was getting paid to do Ruby on rails since then. So it's 20, 20, 24, almost 10 years at this point, I'll round up for sake of that, before that, most of my stuff was WordPress, PHP just dabbling. I always like to build websites, but it was always like front end or using some sort of framework that obscured the back end stuff. Yeah. I always try to dabble.
Brendan:Yeah. It's funny you say that. Cause I had a similar route to where it was like. Even before I, it was between like when I realized, like I said earlier, like when I felt, Hey, I can, I can't be a developer, but like I was interested in the web. So I kept finding what was it? Weebly was one. I don't know if you know if it exists anymore and like things like that. And I kept being like, yeah, I'll do this. And all the while, like my brother. Who was doing PHP is it'd be a lot easier if you just wrote the code. And I was very resistant to it for a long time until finally I was like, you know what, he's probably right. And then that's when I dove in myself, but
Ryan:yeah. I went through a long phase with PHP, right? You start building websites with WordPress and that was, a nice side hustle, if you want to call it that, like I could make a little bit of money, but it wasn't crazy. But like every client I had wanted to customize WordPress in some way so that, now you drop down and trying to hook into the WordPress stuff and you are writing PHP, but it's like a, it's like a component almost, and you're reliant on however WordPress does things. Then I was like, all right, I can do this better. This is annoying. You try to write a full PHP app and you're like there's actually a lot that goes into, that's a lot, right? Yep. Then you, and then you find Laravel, like everyone else probably at some point and it's okay, but like still with that, you're still
Brendan:writing PHP though
Ryan:you're still in PHP. And it was just like, I don't, I didn't like the way. I couldn't wrap my head around that way of thinking. I don't know how else to say it. And it's not a knock on PHP or Laravel, cause they're great languages and a great framework, it's obviously powers a big chunk of the web, but I just couldn't figure it out for myself. But when I found rails, it was like instant, like I get this right. And. I think that's the power of Rails and why people love working with it and Ruby. It just reads like a human reading.
Brendan:Yeah, exactly. That's I think one of the things that DHH always talked about. When I was reading that stuff forever ago, I was like, Oh, this is why Ruby or even just Rails, which is on Ruby is so powerful and why he liked it at the time. And obviously he probably still does. But yeah, it really, I felt the same way too. I think I was at like one of those. Secondhand bookshops. I found this like random PHP book. That's where I started after I knew my brother was writing it. And I remember the same kind of thing where I'm looking through the book and I'm like trying to figure out essentially like loops and things, that sort of stuff, and it just never clicked, but then you get to a block and Ruby and it just did. And so I had a lot of similarities there too.
Ryan:Yeah, that's interesting. Like I've, I feel like almost every, every language has the same constructs, right? Loops, if statements, strings, whatever, right? So like that, that always made sense for me. It was the part of, obviously Rails is nice where it reads better, right? I'm trying to articulate, what it was. And, this was 10 years ago or 15 years ago at this point. So maybe I'm. A little bit revisionist, but it was more like, all right, you have to do all this configuration and you have to actually like connect to a database and you're writing raw SQL. So it's like you're learning many languages at the time. And if nothing else, Rails takes some of that away. So it makes the burden on you to, make the next thing a little bit easier. Yep. But for a long time, it was just like, all right, I have to, you essentially have to write at the time, which either C Sharp or PHP, pre-Laravel, and LetterVel might even have existed then, but I didn't know it. You essentially have to write a, yeah, you essentially have to write a database adapter. Right now it's like, all right that's a pretty heavy ass for someone who's just learning the code. I just want to get a page up, rails, but the, the five minute blog or the 50 minute blog, whatever it was at the time, it's appealing, and it helps you get over that first hump. I obviously never looked back after that and I love. Coding in a way that, at one point I wasn't sure I was ever going to get to. Yep. Yeah. No, I feel the same way
Brendan:too. It is. It's a really good way to put it. It's totally empowering to be like, you can get this up really quickly. You don't have to know everything about everything. You can learn it slowly as you go. I think there's, obviously there's a benefit if you know a little bit about databases and a little bit about networking, but like you don't have to. You don't, you absolutely don't have to and you can get started. And yeah, I remember when I was, Writing PHP for, I don't know, it was probably like a year, maybe something like that. I ended up having a little app that I tried building and similar to what you were just talking about with like database configurations and stuff. I remember having to put the database configuration in every single file. And I wasn't using a framework at all. It was just like me trying to figure it out with, I don't even think now that I think about that book I had, I don't know how much of that was like pointing me in the direction of what to do. I think I also did like lynda. com videos for PHP. And then I know I did some for Ruby on rails too. And there's a site I haven't
Ryan:thought about in a long time.
Brendan:I know. I think I had the rails to like tutorial on lynda. com and then the rails three when I remember when that was new and it's like there was a new tutorial and I remember watching that and I'm pretty sure I had a PHP one too. And that must've been where I was like doing a lot of that stuff. But yeah, it's so different when you go from that to rails and it's it's all, hidden down underneath and auto magical as they call it and all that kind of stuff that I can say like the auto magical thing. I've got a little bit of a love hate. Relationship with, but in general to get someone interested in it, I think it makes a lot of sense and it's helpful.
Ryan:Yeah, I agree with what you said earlier. It's like super helpful to know the underlying mechanics, right? I think the challenge is when you're brand new to anything is that is like overwhelming, right? And that was like, the first hump was like, I wanted to understand. Every piece, right? And if I didn't understand what was under the hood, I had a hard time doing the next thing. And that was like very prevalent in my first few experiences. And Rails balances that line with Hey, they don't, it's not like they hide what's underneath. They just. Abstract it, right? So like you can go in and see what they're doing, and if you really care about database adapters, you can drop down an Active Record and see how it works. Ironically, I've never once done that. I've let go of that notion of having to understand every little thing, because they did a good job of extracting the top layer, right? I can understand that, and I can I guess, what's the right word? Infer. What's happening under the hood to a level of satisfaction that I don't have to ever think about it again. And that was the difference, right? PHP at the time didn't have any abstraction at all. So it's like I have you like you. Yeah, they had like libraries, for certain database patterns, but it was. I had very, I had a lot of discomfort with just trusting it, maybe that maybe we've just come a long way in terms of that. Cause it, it doesn't actually sound that different in hindsight, but
Brendan:One thing too, that. You're just reminding me of is obviously gems are a big part of the rails or the Ruby community, but Rails too, but like looking back, at least my limited time with PHP, I'm sure they had libraries. There's no way they didn't, but it just, it wasn't part of my like universe. I wasn't thinking, Oh, there's gotta be a library in PHP that I can pull in to do X, Y, and Z. But when you go to rails and Ruby, it's sure, you can go way too far with RubyGems, but they were there and that was like a thing I remember almost instantly with oh, you don't have to write everything you could get You know, obviously Rails is a gem and there's all these other gems that are attached to that. But on top of that, you could do a gem for at this point, anything probably, but,
Ryan:I came into Rails at Rails 3 and it was a very brief existence before our app was on Rails 4. 2. So like for the most part I know 4. 2 and above. When did, were RubyGems there from the very get go?
Brendan:They were there as long as I remember.
Ryan:I don't know exactly what that is. That's an interesting paradigm, right? That it's part of the culture.
Brendan:I would imagine, though, they always were, because I can't imagine Rails never was a gem, right? Just thinking about how Ruby works, how it's always worked since I've been with it, it's there's always been the gems that are the libraries you pull in, and Rails has always been in a library, essentially, that lives on top of Ruby, so I would think it makes sense. Yeah. Yeah.
Ryan:I've never thought to question it until just a second.
Brendan:Yeah. No, it's interesting too. I like looking back at this store sort of stuff. Cause it's there's so many things you forget because you just haven't had to deal with them in a long time like that. And I'm just trying to think too, like my first job, the paying job I mentioned earlier was a healthcare startup. And they actually, I think they had a PHP app, but when they hired me, They had just moved to Rails, and so I'm, I know we were on three, and I think they must have started on three and honestly that, where I went on that job, I don't remember if they ever upgraded to Rails 4 or whatever, I wasn't part of that at that point. Yeah,
Ryan:neither was I. By the time I committed my first bug fix, the app was already, had been upgraded from 3 to 4 too and whatever was in between, but that wasn't me who did that work. So who knows?
Brendan:And that, that could be a whole episode on rails upgrades, so we can save more discussion around that for later because I know we both have more experience with it at this point, but
Ryan:yeah, we've got to, yeah, that would be a good episode because I've got a lot to. Contribute on that, having currently going through the process of going from rails for two to the current version. And we're just about to push rail seven. That's awesome. We can definitely talk about,
Brendan:yeah,
Ryan:let's put a pin in that one.
Brendan:Save it for another time.
Ryan:Yeah, totally.
Brendan:Yeah. But yeah, it's interesting though, like I said, to look back and just think about where things were when both of us started and where they are now. And, just the, it's funny too, the similarities that we both have, and I wonder like knowing the people that, that work for me now, who a lot of them were also similar to us where they started in something that wasn't programming. And most of the people that I've hired, they've gone to bootcamps and like neither of us. It doesn't sound like you did. I didn't. And so that's, more of a newer thing. I think they might've been a thing when I was starting, but I didn't really pay attention to it.
Ryan:I remember it was like, there's one or two of them at that point that I was aware of, right? The there's the one that came out I think it was Y combinator I don't even remember the name of it. And then there's, I think Flatiron was around. Flatiron
Brendan:is where I've hired people from before and also Turing school. Those are the two that I know. I know there's plenty more at this point.
Ryan:There's a whole nother episode on the pros and cons of bootcamps, but let's table that one too.
Brendan:Yeah, definitely.
Ryan:So why, why is it that you think you've ended up hiring people with that background? Do you think you gravitate towards that? Or is it been there? There are other forces at play.
Brendan:I think some of it had to do with just like company size and we had a need for people that were I guess fairly junior for a specific reason that actually has nothing to do with rails and more has to do with what we do for our company with the idea that they would come in, they would do that sort of basic thing for lack of a better term, but also be able to do some real stuff on the side and slowly grow into the role. And that's worked pretty well. I think most of the people I've hired that way, I've got, one person that's grown immensely in this, several years they've been with me and now they're writing tons of react and tons of, Rails code. And, they're for lack of a better term, they're on their way to being a senior developer. And Yeah. And that's not always going to be the case. You have to get lucky. There's a lot of people that do that. One thing though, that it's become harder as we've grown as a company though, because for us, we've just got so much tech debt now. And so we've scaled so much that it's really hard to grab a entry level person like that and even give them enough mentoring time to, to grow them. So when we were doing it, it worked out pretty well because of the size of the company and the size of our customer base. But as we've grown, it's become a little bit harder to do. And I think I always had a bit of a, soft spot for someone who's trying to get in like I was sure. So that was something that appealed to me. And then the fact that like we were on rails and react and Flatiron at least was teaching rails and react. Although I may be wrong about this. I feel like they might be teaching PHP now, but at the time they were doing rails and react. And so it felt like a good place to go for where we were as a company at the time.
Ryan:Yeah. That's interesting. Obviously you're. You're being careful about what you say. So you can just say, I plead the fifth here, but would you do it again? Would you take that same approach? I can
Brendan:say right now, I wouldn't do it again at the moment, mostly just because of what I said a couple minutes ago about the size of the data or not the database, but just like the application and the needs the application has doesn't really fit. Another junior person right now. Would I do it again though in a different situation? Probably yeah, I think there's a lot of benefits to it And I just think like the case that the where I'm at as a company and where we are as a company I guess is the only reason I'd say no right now.
Ryan:Yeah, I think I'm in the same boat, right? Like I've had interns, from various college programs for summer internships. I've spent a lot of time working with them, coaching them, pairing with them. And, that is as beneficial to me as it is to them. I don't think they realize that. The old adage, you gotta teach it to understand it is 100 percent true. So that just the sake of explaining it. And of course, having the patience to let them learn is a skill that you have to develop, right? It's not easy. But what I was gonna say is the. We've also accumulated enough tech debt where even with, hiring a, I'll say an average level agency, it's hard for them to come in and really make a big impact. And there, there's no one else to blame but myself, I've let the app get to that point. It wasn't always unintentional, a lot of times you make that conscious decision is I just need to ship this thing. I know I'm taking on more tech debt, but now it's I, I'd almost have to hire a very senior level engineer to have them come in and be productive. Yeah, and I spend most of my coding time now refactoring, cleaning up, adding tests doing the things that I think are going to be important to, bring in different levels of engineering talent. I'd love to have a junior. I'd love to have a mid level. I'd love to have a senior, but my developer experience isn't one. It would be really hard for someone to come in at anything less than a senior level right now just because of the problems we're facing with tech debt. And, it's a catch 22 or chicken and egg, whatever you want to call it is, I got to clean some stuff up to make it easier for people to come in and be productive, but I don't have the time. So it's like, how do you solve that? And I guess the answer is slowly. And patiently, maybe that's another thing we can dive into in the future.
Brendan:Yeah, I would agree. Like one, one thing that I've found and I remember this for myself too, is like a good place for juniors is if you have like an admin panel where they don't have to know everything. And most likely you've got active admin or something like that is going to help them along. And that's a good place to start, but, there's only so much of that work to do. You have to justify hiring a full time person to mostly do that sort of stuff and whatnot too. But, that's something I've seen work and it also, that worked for me when I started, for a little while anyways.
Ryan:Yeah, that's a good point. Something I'll think about. Cause I do have quite a bit of that type of work that could be done. But essentially our whole app is an admin panel. So it's we don't do anything, super great. Like almost everything we do is crud, right? There's just lots of controllers and views and forms. Just naming has gotten in the way. Yeah. I've made some bad naming choices that makes the domain harder to understand and unwinding those is not a hard thing to understand, but a difficult thing to implement.
Brendan:We've got that stuff too. I think every app has it to a certain degree, and we've actually had discussions recently about that. About, what do we call it? We need things to not lie to us, basically. That's the way we think about it. And yeah it's not non trivial, it is a challenge, even if it's just renaming something.
Ryan:Yeah, it's just easy to mess up, right? Or to miss one instance of it. And if you don't have a test suite to back you up, then it's it's just risky, right? So again, it's, it's one of those things that it's do I spend time adding tests or do I spend time refactoring? And the truth is you got to do a little bit of both at the same time, in my opinion. But that's. You got to be disciplined to spend the time on it. And that's not easy when you're a boss or in my case, myself is telling you, Hey, you got to get this feature done or whatever.
Brendan:Yeah, that's a whole other episode right there too. Just struggles of where do you call it done? So you can move on to the next thing. And what do you prioritize as the next thing and all that kind of stuff? Yep.
Ryan:Yeah. I think that's another good one. All right, so we've done our developer origins. We've had a decent conversation here. We've teased about four or five different topics for future conversations. Do you want to, start to wrap this up and call it a episode one?
Brendan:Yeah, I think we should call it. Thank you for listening to the Rails Business Podcast with Brendan Buckingham and Ryan Frisch.
People on this episode
Podcasts we love
Check out these other fine podcasts recommended by us, not an algorithm.
Code with Jason
Jason Swett
Standing in the Fire
Very Good Software
Remote Ruby
Chris Oliver, Andrew Mason, David Hill
IndieRails
Jess Brown & Jeremy Smith
Startups For the Rest of Us
Rob Walling
Vibing with AI Code
Brendan Buckingham