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
Jess Brown
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
In this episode, Jess Brown, shares his journey from freelance consulting to becoming a Rails developer and business owner. Topics covered include Jess's origins with development and Rails, his roles in his businesses, Bootstrap upgrades, mobile apps and more!
00:00 Introduction to Jess Brown
00:12 Jess's Journey into Development
01:05 Transition to Rails
03:29 Business Ventures and Roles
07:30 Building and Managing Apps
12:46 Challenges and Solutions in Development
16:46 Upgrading and Modernizing
19:34 Bootstrap and Rails Upgrades
20:35 Dependency Management Challenges
23:16 AI in Development and Code Review
27:14 Using Videos for Task and PR Reviews
29:27 Buying and Growing Businesses
34:50 Conclusion and Contact Information
LINKS
- CSePub
- Tract
today we've got Jess Brown with us , and he is one of the co-hosts of the IndieRails Podcast and also a business owner and a Rails developer. So welcome to the show, Jess.
Jess:Yeah, thanks for having me guys.
Brendan:With all of our guests, we like to start with, your origin with Rails or developing? Yeah, where'd you start?
Jess:Yeah, so I, I actually didn't, I started out doing, cons, freelance consulting and just building like marketing websites. And I was like just learning CSS and HTML and started dabbling with a little PHP. Of course, that led into like a little more functionality, a little more functionality. I. Customers wanted like CMS functionality. So I got started with JU Law. I don't know if you guys remember that. And then there were, like any open source system, there were plugins, you know, open source plugins you could pull in. And they worked like, mostly as advertised. But then. You'd always have a customer say like, well, can you customize this feature or can you do this? And I remember like, trying to get into that open source PHP code and just feeling so lost and overwhelmed. And at some point I came across like blog articles and like everybody talks about, uh, with rails. And it was just a breath of fresh air. And I was like, okay, I can do anything with this rails. It, it gives me this superpower. And, you know, compare that against, like fighting against this. Other code that I really don't understand how it works and this is understandable to me. And from there on I was like, alright, I, I also never really found a really good fit on the marketing side of things, like with the business websites. And when I started doing development, that was like more my style. I was like, alright, this is it's not so subjective, copywriting design is subjective, but. If I can program something that is objective and I can like, okay, it does work. And I like that.
Ryan:That's a really interesting sort of point, right? Because if you look at code, I mean, there is obviously some objective pieces, right? If you don't get the syntax right, like it doesn't compile, doesn't build. there's a subjective side too, right? So it's like
Jess:Sure.
Ryan:and it's like, you know, there's code style, there's, you know, approach, there's, you know, functional versus object oriented. Do you get into any of that or, does that part, make you uncomfortable?
Jess:I think I do now. I probably didn't know as much as then when I was first getting into it, but yeah. Uh, your user interface you know, how you organize things is I. Obviously very subjective, and you can you can have code that works, but like nobody knows how to use it. Uh, as a matter of fact, one of our businesses that, um, I'm in now, we the, it's actually like a version two, and the first co-owners had a working version and the code worked, but nobody could figure out how to use it, and it would just, it was like unusable basically.
Ryan:Yeah, that's, that. That's interesting. I, I, I think I feel the same way about you with the going from, you know, I did marketing and I still do some, that was my job versus now it's just sort of part of the overall business picture. Marketing is very subjective and that it's hard to like, pin down and, and measure, uh, a lot of it is, you know, difficult to prove ROI on
Jess:attribution. Yeah.
Ryan:there's, there's definitely a, a pull towards just like, Hey, it works, it's usable. It's in the browser. That's nice.
Jess:Yep.
Brendan:Yeah. And as we've mentioned, you're a co-owner in a couple businesses. I'd love to dive into, what those businesses are like, what your role is in those. And obviously we start with rails, but are you still writing a lot of code, for instance,
Jess:yeah.
Brendan:wanna talk about there?
Jess:Yeah, sure. So in, um, 2013 I built an MVP for a couple of guys that they owned a bunch of college textbook stores and they started to see the writing on the wall. Things were getting digitized and they wanted to be a part of that. Through just a referral through a, a website, uh, client that I had. They came to me with their business idea and it was like perfect for me.'cause this really was probably my like maybe second or third like real Rails app. And so we, we built the MVP and at first it was just to publish some content for professors and, you know, if, if. If you've been to college, you probably know that. Like there's, they print these handbooks or you might have these handbooks for like labs and classes. And that was like the original goal was just to be able to digitize that. And then over the years we've, we've grown and we've gotten in contact with new professors and we've built out. Additional publishing tools and mostly the assessment side of things. Being able to have quizzes and, um, questions. We do some custom integrations. We just built a mobile app for kinesiology classes to track steps and then you can grade step goals. And um, but where, um, and then my other business is. It's called tracked and it is, it's pretty unique. It's a, um, forestry management tool for timber buyers. And timber buyers are kinda like general contractors for the timber industry. They go out and find landowners who wanna sell their timber, and then they consult with, or they contract with, uh. Logging companies, trucking companies, and then they also have relationships with the mills. And so they put all these pieces together to harvest the timber and our app tracks the, the load from the job site all the way to the mill. And we do all the financials and accounting on the backend side so that, you know, when. When the load comes in, there's a lot of parties involved. There's the landowner has to get paid. They get, they have receivables from the mill. They have to pay the logging company, they have to pay the trucking company, and there's usually consultants and things like that involved. So there's just receivables and payables going everywhere, and we track all that and handle it. It's also like a project management tool, like we can, they can manage their job and there's like so many things that go into setting up jobs and contracts and pricing and all that stuff.
Ryan:So both of those, both, both of those apps feel like there's a lot of meat to 'em. So how do you balance your time between the two apps? Are you involved with both equally? Do you have other partners? Um, you know, what's your role there? I.
Jess:Yeah, so, both companies are really similar. The, um, the publishing ePublishing platform, there were two original co-founders and so they help with one, uh. Does a lot of sales and like organization other does a lot of support. We've remained really small for that team. We're really lean. I have another developer that helps me out a good bit on that project, but we. We don't have a, a huge team. And then on track it's a father and son. The father was involved in timber industry for like 30 years, and so he had that deep industry knowledge that really helped us get a footing into the industry. And so he, he handles a lot of the sales and the son kind of handles the administration and leadership role, but on track we've been in growth mode for probably like the last four or five years, and we have three other rails developers a front end guy and a full-time mobile developer. And then occasionally we have some contractors in addition to that.
Brendan:Yeah. One of the thoughts I had when you were talking about Tracked originally was whether there is a mobile app involved, and you just answered that question. So now my question goes to is that an iOS? It sounds like it's an iOS or Android or whatever.
Jess:Yeah, we started, um, our mobile developer was a native iOS developer. And yeah, it was, I tried to, for our MVP I tried to make an offline web app and it worked okay. But we, one of the challenges is that we. You think of logging companies, timber, they're way out in the woods don't always have a connection. And so like managing the offline stuff was really difficult, especially in the browser. And you bump up against local storage sizes or file sizes and right away we knew we had to build a mobile app and he was a native guy and then he, he learned how to build on Android. So we eventually built Android and we're actually just done a ton of work to kind of level up our Android app to our iOS app.
Brendan:What's that experience been like to have essentially three code bases, right? You got your rails app that I assume is the API that's talking to those apps, those those native
Jess:Yeah. We have the, the monolith the Rails app that is also the API and then the two mobile code bases. But
Brendan:with, with having all that, or
Jess:no,'cause it's pretty separated. I mean, the, the.
Brendan:Okay.
Jess:mobile developer is in those two code bases, and then we all stay in the the Rails app. I, I don't think anybody even knows how to get to the mobile GitHub repos except for myself and the mobile developer.
Brendan:That's funny. Yeah.'cause I mean, for me, I keep thinking of, just like even side projects and stuff, and of course with like Hotwire and, and all those things. Now you could conceptually build all of it in Rails and it would work on all the devices and that, initially, that's where my head went, was like did you build it that way? Obviously you built it a long time ago
Jess:Yeah, this was 2016 when
Brendan:those weren't a
Jess:we first started building that, and also I wouldn't, I don't know how you would handle the offline stuff.
Brendan:That's a good
Jess:That's still a challenge. And like our, our mobile app uses SQL light now to sort of like cache the, uh, all the entries and then when it becomes online, it sends 'em upstream to the server.
Brendan:Got it. Yeah. Interesting. Yeah, that's, uh, you, you're, you're definitely the first guest where we, we've had iOS and Android in the mix with the Rails apps. That's unique and cool.
Ryan:I was just having this conversation about, do we build a native app or do we do the, you know, the sort of the Hotwire native hybrid thing and the offline was like, the first thing that came up is like, can we offer offline mode? And I think that answer is fairly simply, no, it's not the best experience. If you need offline, you need to go native. Did you run into any other sort of things where you know that you could. about what the trade offs are. I mean, are there other, is there other functionality that you can get in native that is you, maybe common that you can't get the hybrid world
Jess:I don't know about other frameworks, but one thing I love about Hotwire Native is that. It's really a native app that just uses some web views, right? So you can always, it's not like you can't build native. So I think that's one of the, like powers of it, is that you can use a web view for things that work in web views, and then you can build native for the things that you can't. And we, but we built this in 2016, so we didn't even have the opportunity to build it. Hotwire native then. But yeah, we use a lot of we so in the temporary industry, when you deliver a load of wood to a mill, you get like a paper receipt and it's kind of like a receipt you get at a gas pump or whatever, you know, and, but they're all different formats. Every mill's different, and that's how everybody gets paid. So we have to get that data off of that ticket into the system. And traditionally it's. Gone into the truck, driver's truck and they collect a pile of 'em. And at the end of the week, uh, somebody will collect those tickets, take 'em to a office, then they'll get punched into a system. And we're talking about thousands of tickets that have to get punched into a system in just like a few day period.'cause everybody wants to get paid. So what one of the things that we brought to the table is that since we have the mobile app, you can take a photo of that. Picture or that receipt. And then eventually we had to scan API, which made the photo much clearer, crisper, and then people could start entering the data into the system in real time. And then we had AI come out. And so that's really a really fun project where now we can have an AI agent read the data off of that ticket and automatically enter these tickets into this system.
Ryan:That's awesome.
Brendan:sounds really cool. Yeah.
Ryan:And I, I guess the question is, most of that would have to be a native component, right? Because you're sort of tapping into
Jess:Yeah, that's what I was, yeah. The scan API.
Ryan:Yeah.
Jess:Yep.
Ryan:Well, I guess I get my answer then. I'm gonna be building some mostly native apps. I'd love to, I, I still probably will set it up with you know, Hotwire native as I do it, because there are plenty of web views that'll work just fine. But the real sort of heavy integration stuff, I feel like you just need to be down in the native code.
Jess:Yep. That's probably a good bet.
Brendan:So I, I guess one thing that. You didn't answer directly, I guess, or I'm still wondering is what is your role specifically with, with this company? So obviously you're doing some rails development, but are you like leading the dev team? I think you said it's like, three or four people,
Jess:Yep. Yeah, we have three rails developers currently and a front end guide that we are, we're redesigning our website now and we're also upgrading our whole front end, which like people talk about rails, upgrades being difficult, but like upgrading a bootstrap from like a version three to version five is, is not so easy, especially when you have lots and lots of views and you got a bunch of jQuery code and you know, all this stuff that has to be. Replaced and updated. That's a big process. But yeah, on track, my day-to-day has gone a lot more to managing you know, writing up task qa, reviewing prs. I've always done a lot of sales calls, but I. Now it's like instead of me listening to the sales call and, and then, or it's not always sales, but it's like here listening to customers and like, we have this problem. How can you help us solve it? And you know, you have to figure out like, what, what can we do? We have this data, we already have this functionality. How do we solve this problem? And then, taking that and delivering that to a developer so that they can you know, hit the ground running. On CSE pub. I'm doing still development there and, uh, like I said, I, I got one other developer that helps me on that project.
Brendan:Gotcha. Yeah, that makes sense. I was just gonna ask, you know, what, what is your process as far as like, just getting all the, the tickets ready? Are you using a specific system? Are you just kind of using typical Kanban, agile, whatever you wanna call it?
Jess:We use Asana on track and it works fine. I don't really have any,
Brendan:no. Like
Jess:Uh, yeah, no, I'm not hardcore on, on anything. I think, I don't think it really matters what you use. As long as you use something and you stick to it and you like, always use it you like use the features, use the comments and don't be, don't email developer one thing and then put the other thing inana, and then put another thing in GitHub. Just, just use one thing.
Brendan:Nothing drives me nuts faster than that sort of thing where it's just like, where do I look for it? Or I dunno if you guys use Slack, but if you use Slack and then it's like buried in this thread that's got like 20 other things going
Jess:Exactly. Yeah. So annoying when you like, you know, you've seen something then you need to reference it and now you can't find it.
Brendan:yeah, exactly. Yeah.
Ryan:The number of times every day that I have to tell somebody on my team to be like, Hey, just create a ticket and Right. That's usually, I think I'm starting to piss people off 'cause that's like my default response. But I was like, all right, here, just go over there. That's where it all is.
Brendan:am right there with you. Yep. I finally have other people in the company that also say the same thing, but for the longest time it was me just saying, how about a ticket? Let's do a ticket.
Jess:One thing I found it really helpful just recently is that I cut off all notifications from like Asana, GitHub, and like whatever else, and I have a pretty. Good routine now where like first thing in the morning I go and use the inbox and the notification features, the inbox on Asana, notifications on GitHub and just process that stuff because what would happen is I would like see it come in in the inbox at night or something and then it would get pushed down and then I would forget about it and I would not be following up with things properly. But this, this works a lot better.
Brendan:Yeah, I found that too. I actually kinda like the inbox in GitHub You know, I feel like that works pretty well as long as you use that primarily and you're not looking at the emails or the Slack notifications or whatever else you're getting.
Jess:Yeah. One place.
Brendan:challenging for me at least. Yeah, one, one inbox would be great. Right. For all that stuff. I feel like is kind of a tangent, but I feel like you guys had a guest on, on Indie rails that was talking about some, maybe I'm misremembering, but I thought it was something like an inbox kind of thing like that.
Jess:It does sort of seem to ring a bell, but
Brendan:either
Jess:I'm coming up with a blank.
Brendan:said, it's kind of a tangent. I.
Ryan:I wanted to revisit what you said about upgrading from Bootstrap three to five and the jQuery you got any tips on, how to approach that? I know that's looming for me. and it just. It's gonna be a big project 'cause it just touches like every file. And I, I don't know if there's any way around it, but if, if you've seen something that works, I think a lot of people probably are in a similar situation.
Jess:Yeah. So you would think that you could just, um, vendorized your current assets, right? And just create a JavaScript file, CSS file and just make that static. And then I. Upgrade to the new thing and then start to move everything over. But if you're using Turbo, it actually makes that a little more difficult because I think what a lot of people might forget is that when you load a page in Turbo, it loads all the assets, right? And then when you make a request to the new page, if the new page is using the new CSS, the new JavaScript, it doesn't just leave all the old JavaScript behind it, just merges it into the new JavaScript. So it makes it really challenging to do like a page by page or section by section update to a website. You, you, because if you're gonna switch from one, bootstrap three to bootstrap five, then you can't just leap from one page to the next because it's gonna screw everything up. So what we ended up doing, and this was our front end developer, Chris, he had a really good approach to this, is that he actually. Said, okay, look, we can't like update JavaScript CSS and design at the same time. We we're gonna have to focus on one thing at a time. And he ended up, let's see if I can get this right. He he installed the new bootstrap five. And then he made it so that the CSS styles didn't conflict. And he did that by. Importing each style sheet individually in modules in the Bootstrap five. And he, he had 'em like commented out and then he would, he would do one at a time. So instead of updating like a page at a time or a section at a time, he was updating a module at a time.
Ryan:But
Jess:And that's
Ryan:entire app.
Jess:cross the entire app? Yeah. So like a button?
Ryan:and then you'd do navigation everywhere and then you'd do button. Okay.
Jess:Yeah. And that, that seemed, seemed to work pretty well. We rolled that out with like very few issues. You know, you could barely even tell the difference in the site design
Ryan:That's really interesting. I. You, you got me thinking about other ways to sort of slice and dice this, and I'm
Jess:it.
Ryan:you had considered any of 'em. Right. Does the new HTTP two import maps functionality, would that actually allow you to separate the assets in any way, or does, is it still gonna
Jess:I don't know. I don't know much about that.
Ryan:Yeah,
Jess:'cause we were using the old like Bootstrap gym and then we use V now. And so we have the new bootstrap coming in from V. So we were able to kind of install them side by side, but we only included, certain assets at a time, certain modules at a time.
Ryan:sense.
Brendan:what I was just gonna ask too, like, how did you, how do you have both versions like that? I think you kind of answered it, but I, I'm not familiar with ve, so I. How it works.
Jess:It is a front end
Brendan:Okay,
Jess:tool
Brendan:got it. Got it.
Jess:like ES build or Web hacker.
Brendan:Oh, I see. Yeah. Yeah. We're, we're still too far back on rails.
Ryan:We just finished, upgrading from Rails four, two to seven two. haven't,
Jess:I or heard about that
Ryan:but as of, you know, yesterday I met, I'm working with FastRuby. Know, to do the upgrades or help me with that. Um, Ernesto. Yeah. And I met
Jess:Yeah.
Ryan:that team yesterday and it's like, all right, we finished Ruby, we finished rails, like we're up to date. we're looking at dependencies. And it's, it was like, you know, all the air went out. It's like, I thought we were close and then all of a sudden I realized, we know we've got, gems that need to be updated. Along with it. Now, a lot of them are minor things, but there's a handful that are like jQuery's on there which I'm, I'm just, makes me shudder a little bit. Like I, I know I gotta do it and I wanna do it, but it's gonna be a hard project. And then we have some other like big dependencies like Elasticsearch that need to be upgraded. So I'm just, you mentioned jQuery and it was like fresh on my mind.
Jess:We did that same thing where we, we were on Rails four for a long time until we like lost long-term support. It was like, all right, we finally gotta do this. And we, once we did it, I was like, from now on, we're gonna stay current on everything and it's we have to pin a bot and it just, every time there's an update, we try to just pull the trigger and do it.
Ryan:Yeah. That, that's my, my dream. Like that's where I'm trying to get to. And we have a legacy. We have another application that we don't do quite as much with. and that, that's also Rails four, two. We ended up using the LTS drop in replacement for Rails on
Jess:Yeah.
Ryan:So anyone else who's listening who needs to go through the upgrade process? You got a couple different, a couple different options there.
Brendan:I noticed that this must be a setting , but a newer repo that I've got depend bot will actually open pull requests now for dependencies that it thinks needs to change. I don't know if you've had any experience actually using that or if you have it turned on or
Jess:Yeah, that's, I think I didn't know it worked any other way, really. I think it'll, I think there's like one mode that will warn you about security issues, but then
Brendan:that's the mode I've seen where you like, get the email and it'll say like, Hey, you should upgrade these. But I, is like, again, a new app that I'm just kind of messing around with, and all of a sudden I'm getting these, like new pull
Jess:yeah.
Brendan:I'm the only person that knows about this. What is this? And then, yeah, that, that's what it was.
Jess:And it can get kind of noisy too. But um, there's a way that you can tell it to only warn you about minor versions that are patch versions, which is pretty nice.
Brendan:I did see that there. There was something, 'cause this was like a, for me, it was like a net new Rails app. And I forget, it was like R Spec or something. All of a sudden it's like, you gotta upgrade this. And I just said, no, just ignore it. So yeah, it was like pretty easy to do, but
Ryan:I had no idea this was a thing. I need to look into this.
Brendan:There you go. Yeah. There something new today, Ryan.
Jess:What's cool about it too is that in the pull request, it'll show you the change log between the current version you have and the new version, and it really helps you to see like, okay, it looks like, like nothing important has changed, so I can just merge it.
Brendan:Yeah. So you've had pretty good success with that. It sounds like you typically will just merge it.
Jess:Yeah. Yeah.
Brendan:Cool.
Jess:I suppose we probably had a few little hiccups, but by and large it's been pretty straightforward.
Brendan:This sort of goes into another topic that's kinda related. I keep thinking, you know, we were all at the same Sun City, Ruby, uh, not the past one, but the one And there was the talk about ai and there was, I think one of the things that, it's drawing a blank on who actually did it. You
Jess:Obie Fernandez.
Brendan:you. Obie Fernandez. I knew I,
Jess:Yeah.
Brendan:the name would come. You know, Obi was talking about like, where's the AI linter for Rails or Ruby and all that kind of stuff. And that's kind of stuck in my head and, you know, that's sort of what this is, but it's not really ai. But, I, I keep thinking like, when can I get AI or something a little smarter than a linter to comment on a pull request or like do the initial review. I still want a human involved, but we all work on small teams. Like what? What are you doing with AI as kind of like a separate thing? Maybe it's not that specifically, but like how's AI helping you?
Jess:So we all use it in our, you know, either GitHub co-pilot or cursor. So it's helping us to develop more quickly. We're not using it anywhere in our like CI or PRS yet, but it seems like I did read something about copilot is able to offer some feedback on prs.
Brendan:Yeah. Yeah. I think there was another product too. I'm, I'm sure if we all went into GitHub right now into their marketplace, I'm sure there's like 10 of these things and we just haven't paid attention to
Jess:Yeah, it's hard to keep up.
Brendan:I. It is. Yeah. And it also kinda speaks to, none of'em must be amazing or something that we aren't all jumping at it yet, right? It's not saturating the the market yet, but it seems like there's an opportunity there and beyond just like helping with coding and stuff.
Ryan:How would you. I mean, it seems like a training problem almost like I, I wouldn't trust AI to do code review.'cause most of the time I don't trust the code recommends as I'm doing something. That's not to say it's not helpful. Like I also use, I, I could not work without it at this point, but there's always, I always review it before it goes into my code base. Right. And most times there's some tweaks it's like. How, how would it be much different than you know, a Linter, robocop, or any of these others where you set rules?
Brendan:a whole lot. Yeah, I don't think it's a whole lot different. I just think it, it's maybe a little smarter. That's kind of where my head goes, but, you know, 'cause one thing I've struggled with and I like, do, do you use a bunch of lynchers at all? Jess?
Jess:No, we don't.
Ryan:Me neither.
Brendan:Do you even use RuboCop? I mean, we, we just started using standard in
Jess:We use standard. Yeah, but it, and, and we have a workflow for it, but we ignore it.
Brendan:But I mean, any linter in my mind, it, it really comes down to I don't want to be the person that goes to the PR and I have to tell you like line length or any of the things that standard can just do, right? So I want there to be a human doing the PR review for the important stuff, but I don't want you to have to focus on that little stuff that really doesn't matter at the end of the day, but. want the code base to look good or whatever it is, that's kinda where my head's at Ryan, though. I'm not thinking like
Jess:It.
Brendan:pr We would not need a human anymore. I'm not to that point at all either.
Jess:But it could pinpoint things that are standouts, right?
Brendan:Yeah, right. It could just kind of help lead you a little bit into the right direction maybe.
Ryan:Yeah, I was just trying to make the leap from, linter standard to AI and like what the difference would be. Right? Because I, I, I would imagine, I don't use Linter yet, right? I don't even use Standard. It's on my sort of to-do list. But I'm a, mostly solo developer on, on my app, so it's like I don't have to manage a lot of that. But it feels like a lyncher would get you most of that. So what does AI add? And this is pure curiosity. I'm not trying to poke holes. I just don't understand.
Brendan:no, totally. I don't know the answer. That's what kinda where we're at.
Ryan:Yeah. Cool.
Brendan:kinda an
Ryan:I like it.
Brendan:being on small teams, like trying to figure out where the efficiencies are.
Ryan:Sure.
Jess:I will share, I think it's probably similar to the goal of what you're talking about is something that we use and I think is very effective is, um. We do it both ways. When I deliver a task to a developer, I usually will have a video that I do a screen recording and I say like, okay, here's what we have. Here's what we wanna do. We wanna make like this thing, do this. And, you know, now I might pull up some code and say like, you know, I suspect we'll probably use like this model and maybe we'll need to add this column or, and like, go over it and sort of give them a, a head start, especially if it's a, a newer developer that may not have quite the context and then. Whenever one of our developers submits a pull request, they always do a demo video of them QA in the feature explaining like how it works, explaining like how I can set up a test to test it out. And it's just so helpful 'cause they can in like two or three minutes they can. Get things started for me. And a lot of times I can do the PR without even looking at the code because I'll see a few things that already need to be changed before I even review the code.
Brendan:Yeah, that's cool to hear. We, we do something similar too where we I
Jess:I.
Brendan:have my team have the video and demo it. Yeah. I, I like that step you said about like, using it to also get you going a little faster, but with your review. But yeah, we do that too. It is powerful.
Jess:And I, I, I can't tell you how many times because I used to do that too with my partners when I was showing them a new feature or a lot of times a customer. And I can't tell you how many times I think I'm done and then I go to record the video and I find issues or some QA issue or some bug. And so it's, it's a great way to like QA yourself.
Brendan:Totally. Yep.
Ryan:I might have to start doing that. I don't have anyone to report to, but I always, you know, anytime I do a PR or you know, a new feature, I'm telling the team about it. Still a good habit, I think.
Jess:Well, you could even release it to your customers, like if you have a, a change log or like a marketing blog and you're like releasing a new feature, like here's the video.
Ryan:yeah. I def I definitely need to do that sort of product announcement. Email has been on my, uh, to-do list for way longer than it should be.
Brendan:Yeah. Yeah yeah. One other things, just switching gears a little bit here Jess, I know like we've talked about again a couple times, is you're, co-owner of a couple businesses. Like, have you ever considered, or I feel like maybe you've talked about this in your podcast, about open to maybe, you know, buying another business or joining another business or something. Do you wanna speak to that at all?
Jess:Yeah, so I, I guess it's my finance background that sort of. Gets me interested in this concept. But just a few years ago I learned about this idea that you could buy a business. And I guess I never really knew that you could do that. Never heard of people doing that. You know, of course you hear like these big mega corporations acquire different corporation, but never really heard of people buying and selling businesses. And of course I because, I was interested in when I first started and became co-owner of this businesses, I was wanted to know well, how can I become a part of this business? And a lot of my entry way into those business was more along the sweat equity lines, but, this concept of like buying a business outright was new, and I don't know if you guys have ever explored it, but it kind of works out where like a lot of small businesses sell for three x to earnings and if you invest in the stock market, you might know that. Typically for like a company, you pay 20, 30, 50 x earnings. You know, it's all speculation and future earnings. But for a small business it's much lower obviously.'cause there's, there's more risk and there's less of a market to do so 'cause they're not publicly traded companies. But I just really like this idea and I've, I've seen other people doing it and I think my personality, I guess going back to when I was doing consulting. I like everybody else that was in consulting business, wanted to create their own app, and I just never found anything that I was in love with enough that I wanted to stop what I was doing and just build it. Sure. I had a few like side projects and chased a few little things here and there, but I always thought that to. To start a business, you had to like invent something, build something new that nobody ever thought of. And of course that's not really the case anymore. But I never could like, invent that thing or find that thing that I was willing to just like bet it all on. And the great thing about buying a business is that you don't have to do that. You, you can take something that's already working, something that's already validated. It already has customers. It usually already has a team in place. It has revenue coming in and. You know, it's, it's a, a bundled deal, right? And that was just really attractive to me. And that you could do that for three x earnings. Like you can earn your money back in three years. That's pretty remarkable. And I think a lot of other people have found this out too. There's there's the Harvard, I got the book over here. Harvard Business Review released a book about five or six years ago, I think it was about buying businesses like this. And there's people coming out of prestigious business schools that are buying like. Heating and air conditioning companies and rolling them up and building big businesses out of 'em. So yeah, I don't know why I, I've, uh, I've enjoyed learning more about that concept and like I listen to a lot of podcasts about it and I've had people on our podcast about buying businesses. I haven't quite gotten to the point where I can figure out how, like I'm not gonna leave my current two businesses. And to buy a new business would be pretty difficult, but what we are looking to do is potentially acquire into those businesses. So if we found like another educational tool, for example, that would compliment our business, then we could potentially buy that and grow through acquisition. And same thing with track.
Brendan:Yeah, that makes sense. And that was gonna be one of my questions too, was like, what? When you are looking at this, like, are you looking at it from a perspective of, of yourself or your company? It sounds like your company's mostly, but
Jess:Probably, yeah. But you know, you never know. Like if, if you came to me and said, Hey, I'm not interested in this business anymore, and it's, it has like X revenue and you know, I just, I'm gonna have to let it like die. If somebody doesn't take it over or buy it from me, then I might be interested in doing something like that. Depending on how much it was, I couldn't. And the other big thing too, is. How much time would it consume? Like, would I have to spend a hundred percent of my time on it then? No, it's not possible. But if I could spend a little bit of time on it, learn about it, and then maybe take some people from my team or hire somebody new to help me handle it, then it could be a possibility.
Brendan:Yeah, and I did re remember your episode. We talked about this pre-call, with the person that was talking about buying businesses. And so it's, it's been on my mind a little bit too. And the, the thing that always pops into my head is like, how do I find the rails apps?
Jess:Exactly.
Brendan:the right way to think about it, but like, that's what's always in my head.'cause I'm like, well, I'll just be the developer on it. But, there's probably a lot of different ways you can skin that cat. And that's not exactly the way to think about it, but.
Jess:Yeah. John Maker and I talk a lot about that and it's it's like, uh, combining all the things that you like, buying a business. If it's a Rails app, then you know, you already know, you feel comfortable with it. And It's a, a good partnering
Brendan:ryan,
Jess:got a Rails app for you, you wanna sell, or at least just wanna talk about, let me know.
Brendan:Sounds good.
Ryan:So maybe.
Brendan:a good place to wrap it up. Is there anywhere you want people to find you on the internet?
Jess:I'm b Jess Brown on Twitter, and uh, let's see what else I got a blog b jess brown.com. I write some articles there sometimes. And if you wanna check out our businesses, it's get track.com and cse pub.com.
Brendan:Cool. And I would also encourage you to listen to
Jess:Oh, sorry.
Brendan:The
Jess:Thank you for plugging it and thank you guys for doing this. I, uh, I wanted to encourage you Chris Oliver was on probably like our maybe fifth or sixth episode, and Chris is just such a bubbly. Warm guy. And he was, he was so encouraging and that meant the world to me that somebody from another podcast would be encouraging us and just saying like, we enjoy the podcast. You should be doing this. And, uh, so I just wanna return that to you guys and say, I'm glad you're doing it. Um, I've been enjoying and listen to the episodes and keep it up.
Ryan:Thank
Brendan:Thanks.
Ryan:you.
Brendan:that.
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