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
Adam McCrea of Judoscale
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
In this episode, Adam McCrea, owner of Judoscale, shares his journey from corporate IT to starting his own Platform as a Service (PaaS) business. Adam discusses his preference for Rails due to its productivity and developer happiness. The discussion also touches on the company's small team dynamics, marketing approaches, and the role of AI tools for development and business operations.
00:00 Introduction to Adam McCrea and Judoscale
00:22 Adam's Journey with Rails
04:59 Transition to Judoscale
05:17 Building and Scaling Judoscale
08:42 Technical Challenges and Solutions
13:05 Marketing and Growth Strategies
21:40 Future Plans and Final Thoughts
Links:
we have Adam McCrea with us. Adam is the owner of Judoscale, a platform as a service business that helps you effectively scale your app. Welcome to the show, Adam. We're really excited to have you on.
Adam:Hey, thanks for having me guys.
Ryan:As we mentioned pre-show, we'd like to start out with sort of a lob for you. But what drew you to Rails and why do you choose to use Rails for work?
Adam:Yeah, I was, I've been doing Rails since 2007. And at the time I was working for Nationwide Insurance here in Columbus, Ohio doing the corporate IT thing, writing classic ASP and getting into Java and, not loving any of it. I was, I was happy to be programming for a living. It, it was,
Ryan:I am the Director of the Department of Health And Human Services at the University of Chicago.
Adam:It was a fine job, but I started getting wind of this rails thing and the thing that got me more excited than anything was the getting real book from 37 signals.
Ryan:weeks ago, you mentioned that you were actually in China for a visit to China to see your father at his
Adam:Got obsessed with that thing. I actually Printed it out using Nationwide's printer and hole punched it, put it in a binder and I, I read it in like a three ring notebook many times and I was like, this is the way I want to work small teams shipping quickly. And the tooling that they use is. It's this Ruby on Rails thing that I don't really know anything about. And I ended up buying Agile web development with Rails. One of the, either the first or second edition, I'm not even sure which one it was back then. But yeah, I just fell in love with it. And I was like this is great. I, you started building some just some toy apps, just playing with it and was able to get a job. At a local consultancy that was doing Ruby on Rails and, said goodbye to corporate IT. And since then I've been doing Rails. I've been on small teams and I've been loving every minute of it. I
Brendan:Yeah, that's awesome to hear. I have a similar memory. I don't think I've read it probably as many times. It sounds like you did, but I remember going through a similar experience with that book, you've been doing rails since 2007 you started out with a consultancy and now obviously you own your own business. What's made you stick with rails?
Adam:There's just a lot about the ethos of Rails that speaks to me. I love that it's it's designed much like Ruby, the language it's designed for programmer happiness, and it's always. That's always resonated with me. I think the, I love the Ruby community. And I've always just felt super productive in Rails. So I haven't really found a need to go elsewhere. I guess I would say I think there's a lot of different kinds of programmers out there. And I'm not the type of programmer that. Gets joy from trying a bunch of different languages and trying a bunch of different frameworks and things like that. Like I found something that works really well for me and at that point okay I was just like, okay, now what can I build with this? And as long as I can keep building things quickly and enjoying that process yeah. I've just got no desire to leave.
Brendan:Yeah, that's cool. I had a little bit of a stint where I looked at elixir and I gravitated back to rails. I also felt similar to you too, where it was like I like what I'm doing here. It does the job. if I wanted to start a new app or if I want to just continue building, I enjoy working in Rails myself. You probably feel the same way. Ryan?
Ryan:You know I do, so thank you for that, leading question, but
Brendan:This is for the audience.
Ryan:yeah. Yeah, I think Rails is just, for whatever reason, it was the language that I was able to understand. Right. You know, you could say that it was written for developer happiness. It is, you know, it, it tracks away in the right sort of way. You don't have to get bogged down in the details, of other languages. And, you know, my journey, it was like HTML, Perl, PHP, WordPress, more PHP, left the industry for a long time, came back, tried again, ended up in rail. So, yeah, I mean, I. I wouldn't be a developer if it wasn't for rails. And you know, that's why I still use it for me personally. But you said you, you like building things you're in rails. So maybe, can you tell us a little bit more about, judo scale and, you know, how rails fits into that equation? I mean, is it, is it, does real power that entire app? Is it the monolith? Is it microservices? Like what's your approach to rails that, you prefer?
Adam:I'll start with just a little bit of a backstory on where Judoscale came from. So like a lot of developers, I just had the dream of, building a side project that, that I could evolve into a self sustaining business and then eventually do that thing full time. Throughout the years, had a bunch of ideas that I would start something, never really commit to it, never really bring it.
Ryan:Yeah.
Adam:But in 2016, the company I was working for at the time real small company and after I had joined them
Ryan:Uh,
Adam:From Engine Yard to Heroku saved a bunch of money in the process, but we were still wasting a lot of money just by having a whole bunch of, server resources dynos and Heroku Running on the off hours when they didn't need to. We're like it would make a lot more sense if we could just automatically scale them up and down. As needed. And there were a couple of different auto scalers for Heroku available at that time. And we tried them both and they just didn't work that well. I got that itch that we often do as developers, which is I could build a better version of this thing. So that's what I did. I asked my boss at the time, I was like, if I. If I build this thing in my spare time would would you care? Would we use it? Would I own the IP? And he's yeah, I don't care. But we were a small company. It was very informal. So I built the first version, what was then called Rails Autoscale specific to. That app you couldn't sign up for it. It didn't work with other apps. There was no UI. It was you managed your settings through a production console. Like there, it was as MVP can get. In fact, there was no V it wasn't viable. It was. It was just a tool that worked for us. And I thought, okay, if it works for us better than these other tools that are out there, then I can evolve it into something that I could sell. And it worked really well for us. So I spent a couple of months, building a basic UI for it and the ability to integrate with the Heroku. Marketplace, which that part was pretty easy and launched it in 2017. So fast forward a few years it just kinda sat there in the marketplace. I didn't do a lot to market it. I was just letting customers find it through the marketplace, sign up for it. And I would, just use customer feedback to keep making it better. And it just slowly grew over time to the point where I was able to go full time on it in 2021. And that's around, that's the same year that we rebranded from rails, auto scale to Judoscale. So that we could be an auto scaler, not just for rails, but an auto scaler for multiple platforms.
Ryan:What's the background on the name? Okay.
Adam:Actually again, ties to 37 signals, 37 signals, a long time ago. One of their little. Internal bits of jargon is using judo as like a shorthand for doing something quickly
Ryan:Uh,
Adam:Effort, let's judo this. Or can you judo that, like just find a quick way an efficient way to get it done without spending too much time on it. And I was just I was just the thought that was like fun like fun internal jargon to use. And it sounded cool at the end of the day. I wanted. I wanted something scale and I wanted it to be memorable and sound cool. And so that's so Judoscale stuck.
Ryan:I'm always fascinated by that kind of stuff.
Adam:Yeah. But you asked is it still built in rails? It's still completely rails. It's a monolith. I say monolith, but it's not a. Big app, like it's in terms of SaaS products it does one thing and it does it well, it doesn't do a whole lot of different things. It's a, it is a legacy code base that has existed since 2016. It has its dusty corners like any other legacy app. But but it is all rails. Currently Rails 7. 2 we'll get it up to Rails 8 here pretty soon.
Ryan:was just about to ask what is your journey been on the upgrade process, because in 2016, I don't know what the current version was when you started, but that's
Adam:I should
Ryan:that's a long time ago. And, and rails land right
Brendan:Must've been four or five, I would
Ryan:somewhere in there.
Adam:yeah. I've never really felt the need to, be on the bleeding edge. Like I want to be somewhat current a little further behind now than I'd like to be, Rails 8 has been out long enough. I'm definitely feeling the itch to upgrade. I think we have one gem dependency that has just held us back a little bit there, but yeah, we'll be on Rails 8 soon enough.
Ryan:that's interesting. Do you have like a, you know, a time frame in mind of how far you'd ideally like to be behind the edge? You know, I'd like to say I'd like to be about a year behind, you know, six months to a year, depending on what the changes were. I'm not there yet. I'm working on it. You know, I'm behind, just like a lot of people are. We're working on the 7 .1 upgrade right now, so I got a little bit of ways to go, but we're getting closer. But what's your take on that? Do you have a number, or is it just sort of when you get the itch?
Adam:It's when I get the itch, like I would say probably roughly if it's been three to six months after the public release I'm definitely going to be feeling the itch to, to upgrade.
Ryan:That makes sense to me, just because, you know, if you're too close, there's still bugs, gems haven't upgraded, and if you get too far away, then you're missing out on, you know, the security, the upgrades, the performance impact, all of those fun things that are beneficial.
Adam:Yeah.
Ryan:curious because, you know, you're clearly a big fan of 37 signals as I think probably all of us on the call are, you know, what other things have you borrowed from their ethos as you've, you know, either use rails or built judo scale, you know, there are other frameworks or, you know, things from, from any of their books that you have, you found useful in your day to day.
Adam:I think it's at this point, it's probably a lot of their philosophies have just ingrained their way into my brain that they become automatic and I don't think. Of them as coming from 37 signals. But I think a lot of the way I think about product development comes from them. I think about one of their, one of their things I remember from getting real was build half a product, not a half ass product.
Ryan:Everyone.
Adam:with, leaving some of the bells and whistles off, it, it doesn't need to be all things to all people. So yeah, we recognize that not everything we build is going to be for everyone. It's not going to do all the things and that's okay, but it needs to be really good at what it does.
Ryan:Yeah. What size team do you have? Is it just you? Do you have other developers?
Adam:It's me. I've got a full time developer, Carlos Antonio, who lives in Brazil. He's actually a Rails core contributor. I worked with him at a previous job. The job I had before going full time on Judoscale. So he's the only full timer. And then I've got My buddy, John, who actually lives in town with me, he does a lot of writing on our blog. And he and I get together to, just to co work for a couple hours every Friday afternoon. Just came from there, before before hopping on here with you guys. And then one other guy who, who also helps with some of the writing on the blog. I call it a team of two and a half. There's two of us full time and then a little bit more here and there.
Brendan:I was going to comment on the blog. I feel like I've. More and more I keep seeing judo skill pop up is I'm typing in whatever search and you know I hit a blog post and it's yours so I was gonna ask how you keep up with that sort of thing and The development and all the other things you're doing as a business owner and a rails developer and all that.
Ryan:everyone.
Adam:Yeah, John and Jeff are the two who have been doing most of the writing on the blog recently. And yeah, it really makes me happy to hear you say that you're doing searches and the Judoscale blog comes up because. It's been a continual debate in my mind. When I put on the marketing, my marketer hat should I be doing keyword research, defining the things that people are searching for to make sure we're writing about the right topics and including the right keywords and everything. And I've tried going down that path a few times. And honestly, I. It just ends up in really bland, uninteresting writing, in my opinion. So we don't do any of that anymore. I don't do keyword research. I barely even have any analytics on the blog. We do use plausible for analytics, but I don't look at it probably to my detriment, but, we just write about the things that are interesting to us, the things that we're excited about, maybe the things that customers ask us about and. If we're not interested in it, we don't write about it, even if, on paper, it might be a keyword that people might be searching for.
Ryan:and stick around. Thank
Adam:resulted in a blog. That's a lot more interesting. I think it shows that we're actually interested in the things that we write about and we're knowledgeable about them. So yeah, I'm really happy with how that's turned out and it makes me feel good that, people like you are finding it. Um,
Ryan:I've seen a bunch of a bunch of your posts in various places and I always enjoy the read.
Brendan:You mentioned a minute ago that you meet with at least one of the blog writers and like how much of the blog post is yours versus theirs? Are you just pointing them in the direction like you've got the ideas or is it a combination?
Adam:It's different. So I've got two writers that I work with John who is a close friend of mine, known him for years. He does the majority of the writing on the blog these days and he basically just gets an idea in his head. He says, Hey, what do you think about me writing about this? And I say, go. And then he writes and then he'll he'll just throw a pull request in GitHub and I'll review it in there because all of our blog posts are just marked on
Brendan:Is he a developer too? Is that where he's getting these ideas?
Adam:yeah. He's a developer. And Jeff is also a developer. He's. I'm just going to be the other person who does writing on the blog. And that's more of a typical writer relationship where he and I will have a discussion talking about, what might be some good ideas to write about. And then he'll draft an outline. I'll give him feedback on the outline. Then he'll draft the article and I'll give him feedback on the article. So yeah, I think it's different depending on the writer, but for the most part and then, it's their writing I'm not. I'm not involved a ton. I do enjoy, getting my own writing up on the blog, but it's really hard for me to be disciplined, to sit down and write. So I'm really glad that I've got, two good writers who are helping me keep it going, even when I, when I don't have the time or inspiration to write myself.
Brendan:Yeah. Yeah. Speaking as someone who is envious of you owning a business and that'd be my ideal eventually, like the marketing side of it just like scares the, the development's great, but the marketing stuff's not really my thing. So it's interesting to hear how you're tackling it.
Adam:Yeah. The marketing thing has never been my thing either. And that's, so one of the reasons that I was able to launch rails auto scale and. Grow it slowly over time was because it was in the Heroku marketplace. So that's built in distribution, some built in marketing. I didn't really do anything to market it in those first few years. I don't even think I had a blog. If I did, I only posted to it, maybe a couple of times a year. I didn't know what I was doing. And I was just totally focused on the product and making the product as good as it could be. So I would say, launching into a marketplace is a nice shortcut if, if you don't have the marketing expertise, it comes with its costs, there's platform risk there's Heroku takes a cut of the revenue cause they handle all the payments and everything. But I have absolutely no regrets about that. That has worked great.
Brendan:I believe you guys have branched out to other platforms, right? Not just Heroku.
Ryan:Hello,
Adam:yeah. We're on Heroku, Render, Railway and Fly. And Amazon ECS. Yeah. So total of five platforms. The majority of our business is still Heroku, but yeah, we're trying to make some noise about the other platforms we support as well.
Ryan:I'm
Brendan:How quickly were you able to add each one of those? I assume it's one at a time kind of thing.
Adam:The first one we added was render. And it took the longest because there was just a lot of tech debt built up. Like we, it was like peeling an onion. It was like, we just kept finding more and more places in the code. Where it was clearly built for Heroku. It was like, okay let's make this platform agnostic. And we peel back that layer. I'm like, oh, this is, glued to Heroku too. So it's just like the first integration was the hardest. Cause we had to make a lot of things platform agnostic that were built specifically for Heroku. The second one we built was faster, but it was Amazon. We had to deal with IAM um you know, much more complicated authentication. It was just as integrations go, it was a more complicated integration than render. But we had, peeled off the bandaid of that first one. The last two railway and fly have gone faster for sure.
Brendan:It's cool to hear.
Ryan:How do you quantify the amount of work it takes to maintain those integrations? Brendan and I were talking recently about integrations. And discussing the pros and cons. We've already talked about the pro, right? A built in marketplace. It helps you drive business. What are the costs? Not like money costs, but like, you know, just overall, there pain points there? Does it take a lot to maintain it?
Adam:Yeah, on the technical side maintaining those integrations, there's actually very little cost, for the most part, the integrations with the, with each of these platforms, the integration points are fairly minimal. We need a way to authenticate. It's either going to be an API key or it's going to be none of the platforms support OAuth, but it, it'd either be an API key, OAuth.
Ryan:My name is I'm a I'm a I'm a
Adam:of API endpoints that you hit to, sync up scale and execute scale events and that kind of thing. So the API integrations are pretty minimal. So maintaining these integrations once we have them
Ryan:I'm
Adam:is not too challenging at all. It's been more challenging to maintain. The integrations with various languages. So once we branched out beyond Ruby, we built a Python integration library and a node integration library. And those have been more painful to maintain just because I'm not an expert on either of those platforms. So when bug reports come in, it's like that's when I feel the sinking in the pit of my stomach. It's oh, I got to dive into the Python library and I barely know what I'm doing. Yeah. ChatGPT has been wonderful for that just to so I can ask questions. It's the pair of programmers sitting next to me while I can ask all my dumb Python questions. So yeah, that, that's why we've stopped after Python and node. Because it's just introduced some complexity and some headaches into the business that I'm not,
Ryan:for watching!
Adam:the majority of our customers are still Ruby developers, probably because that's all we write about on the blog. Because again, we're writing about what we're interested in, what we're knowledgeable about. So, Yeah, I think if I really wanted to take seriously getting into those other communities of Python and node yeah, I would probably need to hire somebody who is embedded in those communities, can connect with those communities, can write about that stuff intelligently. So yeah, until then, yeah, the majority of our customers are probably going to be Ruby developers.
Ryan:Would you ever consider dialing back the number of languages or you just kind of sort of comfortable where you are?
Adam:It's hard to Say no to money and we do have customers on each of those other platforms. So yeah, if we only had a tiny handful of customers on each of those other platforms, I might consider it, but we've got enough that it's worth it to keep them for sure.
Ryan:feels like those two are. natural, more natural extensions to the rails ecosystem and say like a PHP, right? Because I feel like node has, has its uses that, you know, alongside rails and same with Python with all the stuff. So, I mean, it makes sense to me, but, you know, it's still sort of new on that front as well. So. Yeah.
Adam:Yeah we tried to basically pick the platforms that we thought were most popular on the hosting platforms that we support, which at the time was Heroku And yeah, as far as I know, the most popular platforms on Heroku are Ruby, Node and Python, maybe Java actually. But my interest in writing a Java adapter is zero. So I don't think that's going to happen anytime soon.
Ryan:I'm with you on that one. I had one more , question on my end is. You know, what are your what are the biggest challenges you run into with rails? You know, are there any that keep you up at night? Or you just sort of comfortable now with, the status quo?
Adam:As much as I have wanted to love import maps. I feel like every time I need to bring in a new JavaScript library, it doesn't quite work how I expect it to with import maps. And I just wish that I could just follow the instructions on whatever JavaScript library it is to get it working with with the yes build or whatever. So right now we are all import maps that might change at some point because. I feel like it just doesn't quite work as seamlessly as it says on the tin.
Ryan:I can't. We're still on like the old school asset pipeline, you know, from the, the, the rails for days. I can't comment on the, all the new fun stuff yet, but, I'm working towards it. So maybe we'll, we'll circle back on that in a year or so and see where we end up.
Brendan:I had a question to going back to, you mentioned ChatGPT, obviously helping out with Python and node and whatnot. And I'm curious do you use it in Ruby development much at all? Or what is your usage there? Because, I'm also thinking like import maps, for instance, like I don't have much professional experience doing that sort of thing. So I'd probably rely on ChatGPT myself or Claude or whatever. Like what does that usage look like for you and your team?
Ryan:governor and then, and then, and
Adam:Yeah, I'm using ChatGPT many times a day, whether it's asking Ruby or Rails related questions or or even marketing related questions Just, bouncing ideas around with chat GPT yesterday about like I said, we use plausible for our analytics, but we don't yet do any like conversion tracking or anything like that. So I was like, Have just looked up on plausible site, but it's really easy when you've got ChatGPT, just as my marketing buddy, help me make sense of all this. And it's great. I also use cursor as my editor and I'm using. Claude within cursor all the time I use the autocomplete. It definitely speeds me up a ton. I don't use the agent like, to actually like generate whole files or any, or whole things of code as much. It's more of the autocomplete that, that really saves me a ton of time.
Brendan:Yeah, that's cool your small team, you've clearly grown enough where you can support two full time people. And, like you said, two and a half people. What role do you think AI actually played in that? Has it made it easier to keep it small or is rails, good enough?
Adam:I mean, AI helps us move faster for sure. I definitely think
Ryan:Hello, everyone. My
Adam:any bigger than we are even without AI.
Ryan:I'm a I'm a I'm a I'm a I'm a
Adam:With or without AI but yeah, I think Rails is definitely part of it. Rails lets us keep a small team and still move quickly. I think even I hired Carlos a little over a year ago and before that, like it was for seven years, just me Huge part of that was being built on Rails for sure.
Brendan:know?
Ryan:For sharing your story. You know, I always love to hear sort of the origin stories of different tools that you see in the rails ecosystem. And, I'm definitely gonna keep a very close eye on what you're doing over there because I like what you're doing. And I appreciate you joining us. But where can people find you on the Internet or anything you'd like to share or point people to?
Adam:Yeah. Yeah. I'm Adam logic on, Twitter, blue sky, LinkedIn, all the things. Also you're welcome to email me adam at Judoscale. com. If you have any questions about anything I talked about today or anything at all, I'm happy to chat. Yeah, thanks for having me on. This has been a lot of fun.
Brendan:Yeah, it's been great having you. Thanks for coming.
Ryan:N.
Adam:care guys.
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