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
John Nunemaker
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
In this episode, Brendan and Ryan welcome John Nunemaker. John is a prominent figure in the Ruby community and, shares his journey into Ruby on Rails, his career evolution, and his unique approach to managing multiple projects simultaneously. There's also discussion around how John and the hosts use AI for their development work. Enjoy!
00:00 Introduction to John Nunemaker
00:19 John's Journey into Ruby and Rails
02:31 Current Projects and Ruby Usage
04:17 The Role of AI in Development
10:51 Balancing Multiple Projects
17:48 Balancing Responsibilities and Focus
19:04 Tracking Time for Productivity
20:06 Daily Huddle and Remote Team Management
20:38 Using Timers and Breaks for Efficiency
23:53 The Beauty and Productivity of Ruby on Rails
26:46 Consistency Across Front-End Frameworks
28:35 The Origin and Success of Box Out
32:56 Future Plans and API Development
34:41 Conclusion and Final Thoughts
Notes
Today we have John Nunemaker with us. John is well known in the Ruby community for his open source work. currently works at Box Out Sports and very good software running Flipper Cloud and Fireside FM as a programmer and owner. Welcome to the show, John. We're excited to have you on.
John:Thanks for having me.
Brendan:Yeah. Let's start out with your origin story. Like what got you into Rails , and Ruby, I know you've been doing a long time, I mentioned you're well known in the community, where did you start?
John:I for? I started, if we go all the way back, I started with PHP, so that was the first thing, which I think there's actually a decent number of people, but this was. Back, yeah. We got a hand raise. But this was back when PHP was terrible, it's like, it was like HTML scripts, everything mixed together. There was no MVC, there was no anything there weren't like popular frameworks, it was like it was like PHP, my admin and like some forum stuff and there WordPress, things like that. So I did a lot of PP and stuff like that. And then I went to, eventually I worked at the University of Notre Dame. While I was there I saw the, build a blog in five minutes, da David's video on that. And I was like, whoa, this looks really cool. I like the language, I like how fast, it was, and this was probably 2005, which dates me. But I was like, okay, this looks cool. And so I like just went crazy. I had no kids and stuff at the time I was married, but I, we would stay up late hacking on and all on the weekends and I just. I started trying to build stuff in Rails and I was like, this is the way, and Ruby and I didn't even understand. I think most people get into Rails and they don't understand what's Ruby and what's Rails. And it's like at some point you realize the difference. And what I found is like even when I've moved off rails into Sinatra back in the day, or Meb back in the day or things like that, I've always stayed in Ruby. I've tried Python, I've tried a bunch of other things. I did a bunch of cold fusion at the University of Notre Dame and the cold fusion. I actually built like generators, like rails on top of it so that I could do things like rails 'cause they wouldn't let us use rails. So yeah, there's, that, that's probably the origin is 20 years ago. Like this, nerdy, still nerdy, nerdy developer sees one video and I was just like, this is amazing. And I made a joke. I remember I made a joke about giggling and snorting after watching the video and like my, and on my blog post and DHH posted that on like the. Rails web log. And so that's my early claim to fame is that I made it on the Rails web log back when it was just him alone, main, maintaining it and stuff.
Ryan:I love that.
Brendan:it. Yeah. That's great. So yeah, you've definitely been doing it a long time. Ryan, did you have a question there?
Ryan:I was gonna say, obviously you've got quite a few different products. I've actually lost track of the company structure, but I don't think it's important. Do you using Ruby slash Rails for all of those?
John:Yeah box Out is Ruby and Rails. It's probably to 7.2 and maybe 3.2 or three on Ruby. And then, fireside is a little far farther behind. We just got to 6.1 and 3.1 I think. But we should be on seven and later versions real shortly. It gets easier, if you're back in the OG days, you remember like from two to three and how everybody just gave up at one point. They're just like, oh, it didn't get as bad as Python, but it was pretty bad back in the day. Now it's not too bad. and then, flipper's the same. It's usually seven two, it's probably the most up to date regularly.
Ryan:Yeah, I'm in the middle of doing, upgrading our app at Local Bowl, and we started at four two at the beginning of this project and we're about to push seven one. It gets easier as you go.
John:It definitely does, and the information available gets better. And the thing that I've noticed the most on, like recent upgrades. Is that having AI to help with it is actually makes it a lot easier too.'cause you can be like I just two days ago I got like this weird, psych bad something error. And I was like, okay, I know this is YAML related, but I have no idea why I'm getting this error. And it was in like literally line five config environment, which is like booting the app and you're like, oh, thanks. That was helpful. And I just pasted it into AI with, no, I didn't say you are an expert at fixing Ruby on Rails or any of that. I just. Pasted it in and it immediately was like, this is your problem and it fixed it. And I
Ryan:Yeah we just had that exact same error I think when we went to seven. Oh. I don't remember how we fixed it, but I'm pretty sure I fixed it the exact same way.
John:It works.
Ryan:yeah. So what speaking of ai, what's your sort of take on where we are in the AI revolution? I hear a lot of people have very differing viewpoints on this and it's usefulness or not usefulness. I'm curious, you've been around for a lot of different things. What's your take?
John:That's a nice way of saying I'm old. Yeah,
Ryan:I'm right there. Don't worry.
John:Exactly. I've been doing this for 20 years. I've been doing it a long time, and I think the thing that I've realized is that like my hands on the keyboard are not my value. And so anything I can do to reduce the actual typing or the actual things like that, it's huge. So I have over, I would say, maybe a year and a half ago, I started like using copilot, pretty regularly. I, maybe six months ago started using like OpenAI kind of directly a little bit more.'cause I just found sometimes for some problems, like it was a little bit better. Maybe in the last three months I've started throwing Claude into the mix. I use AI personally, I use it extensively, but I feel like, the reason that I do, I feel like a lot of people like me, I've seen 'em in the Ruby comedian and they're like, AI is just, spitting out slop and it's terrible, and all this kinda stuff. And I'm like, yes. A lot of the time it's really bad. Like it'll put something out that'll have an obvious error or it'll have, but most of the time it gets 80% of what I want for a one line change or a method change or like a small thing. And it saves me all that typing. That's huge for me in my old little programmer hands, so that's, yeah, for me it's huge.
Ryan:I can't program without it anymore. Honestly I'd be pretty scared to turn off, I use ChatGPT mostly. Although I'm exploring some other ones. If I were to turn that off, I'd become so much less productive. I don't know what that says about how my brain works, but, it's I like to think, compare it to what it was before, right? If you had a problem, what were you doing? You're spending hours sometimes searching stack overflow and finding wrong answers. Trying it, watching it not work, trying, searching again. So 80% good is pretty good,
John:Yeah, and it
Ryan:on the AI front, right?
John:you search Stack Overflow, it's here's pretty close. But you're gonna have to change variable names. You're gonna have to change other things. You can just paste the SQL Query in and just be like, just format this for me. Make it prettier.
Ryan:Right.
John:uppercase the right things. It'll indent, all that kind, even just little things like that. It's amazing. I, I did a long session with it this morning. It's like my, one of my, bros. I'm a big fan of it. Yeah, I don't know. I don't know what I would do either. I, especially taking over fireside, I would be lost because it's like all this server stuff. I was the pink elephant, like DHH talked about at Rails World, like I avoided servers use Heroku. Fireside is not that. It is like on LE node, and it's servers and stuff like that. And I was like, just, I'm like, I don't remember. How do I list the most recently modified file? It's literally like I use AI for everything now for that kind of stuff. Oh, what's a way to do this? Or how do I do this? Or, I started making Ansible playbooks and so I was like, how, like what's an ans how do I do this in Ansible? And it's starts generating it and you can use it and tweak it. It's, yeah, I it's definitely made a difference for me. So
Ryan:Yeah, I learned how to. Manage an EC2 server for the first time from AI when the same thing, like everything I've done has always been on Heroku. We acquired a mobile app that was using EC2 and I was like, I don't even know how to log into this thing.
John:Yeah.
Ryan:It got me through it. I got done what needed to be done and it only took me a couple hours versus, it could have been days or weeks. Otherwise I, you knows.
John:Yeah. It's less of writing the code for me. More just like a smarter, better auto complete. That's like what I would say 90% of my usage is like I start to write something and it, it gets it better. And even recently, I've switched to cursor because of that. And even though I have free copilot because of my open source, I was like, I. It the, I started using Cursor and I was like, 'cause everyone's raving about it. And every time I switch I'm like they're wrong. This is stupid. I don't get it. It doesn't, and the truth is, composer or chat, whatever you wanna call it, like doing multiple files across my entire project. It's garbage.
Brendan:I don't like it.
John:Yeah, it's garbage.
Brendan:all.
John:It does not work for me. Now, maybe it works for Node.
Brendan:most of it.
John:Exactly. Yeah. I'm just like reject. Like not what I want, but on an individual file when I'm just typing and it just, it's yeah you're changing this variable name. I'm just gonna do this for you. The rest of the way you just hit tab. It's so much faster than copilot for some of that kind of stuff. And the complete, it just feels, it's hard to explain 'cause someone was telling me the complete's faster. This my friend Jasper and I, he was like, no. He's the complete is so much faster in cursor and windsurf. And I was like. Co-pilot's really fast. I don't think it could be faster, man. And then I started using it and I was like, oh, it's faster. It just, it, I don't know how, but it's faster and it's more contextually accurate. So I dunno if it's Claude or I haven't tried changing co-pilot to Claude to see if that's, if that does
Ryan:Yeah, that's interesting.
John:it's snappy.
Ryan:I have it installed and I've opened it a couple times. Cursor I need to get back to it for the same reason. You said everyone's talking about it. I need to at least feel like experience it once to make a decision.
John:Yeah, you gotta commit to it for a day or two.'cause didn't, I really didn't feel it the first time. I was like, this is just vs code. Like I don't get it. And then I realized oh, okay, the nice thing is everything imports in and you literally have the exact same setup. You're not changing editors, you might get a little bit smarter.
Ryan:Right.
John:So yeah
Ryan:I first opened Cursor, I was also changing editors from Adam to VS. Code at the same time. And I was like, I can't do both. I gotta get used to VS code first and then I'll come back to Cursor after. But definitely gotta get that higher on my list.
John:Oh, VIM.
Brendan:Vim
John:Wow.
Brendan:to cursor,
John:that's a big jump. Yeah.
Brendan:Yeah, it's still hard. I actually, in fact, I had a conversation with Ryan Castillo in our last episode about this same thing. He and I basically do the same thing. We both work in Vim primarily, but then when we have a question, we'll go to cursor, talk to it in the chat, do our thing, and then we'll come back over to Vim.
John:Is there no plugin or something that would like kind of
Brendan:I just haven't tried 'em yet 'cause
John:Oh, okay.
Brendan:yeah, that, that's the hold up for
Ryan:Yeah.
Brendan:It was easier to install Cursor and try it that way than figure out how to get the Vim thing working.
John:Interesting. I've tried Z as well. I love, I know the team I worked with like Nathan and some of them at GitHub. So I get it and it's way, it's fast. It's super fast. But I just, for some reason, every time I use it, I don't quite, I don't know, for some reason it just doesn't quite resonate with me. I don't know if I'm just too ingrained now with VS code and stuff like that or what, but.
Ryan:It works.
Brendan:a good segue to one of the questions I was gonna ask you, which is, you've got all these things, you've got open source, you've got what three products you're working on, and I know other people work with you, but obviously AI is one thing, but how do you keep up with everything with all that's going on?
John:Yeah, it's hard. I like, it's just balance like a lot of it is just like I'm very much I think some people are like. Lions, like they go crazy for, oh, like they go catch the gazelle in 10 minutes and they sleep for 23 hours. And I'm just more I don't know what the example is, like the little like Marmite that digs all the holes all over the place out west. It's I just always every day show up. Even Saturdays and Sundays I'll get an hour or two and I don't work crazy hours. I'll maybe work whatever. I can't remember the last time I worked 40 full hours in a week. I don't do that, but, so it is not like a lot of time, I'm not just brute forcing it, but I just consistently move things forward. I. day. That's, I feel like the biggest thing, and far as how I do it, it's just I try and put systems in place, so I have like there's a few things. So one for the last six months or a year, I've been tracking my time pretty heavily. Which I don't have to, I'm part owner and two different businesses. And so I don't have to track my time. No one requires of that of me that no one looks at it. Like my partner's on either side. Nobody says, how many hours did you work last week? But for me, that keeps me honest on if I say I wanna work X hours on fireside, X hours on flipper, X hours on box out, am I keeping my word on that or not? And for myself, that, that helps me a lot on my priorities because it's very easy as a developer to, to get nerd sniped. And so you see this like interesting problem come up or thing like that and you're like, Ooh, okay, I wanna work on that. But I'm like but I'm at my hours and what I said I was gonna stick to for this project. So I need to like, not do that right now and make it to do then I'll go to Todoist, which is another app I use, so I use. for T-O-G-G-L for time tracking. And then I use Todoist for keeping track of all the things. And so I have those. And then, as far as like inside those, the systems that I use toggle is just like play pause, and then I'll have a few projects, box out. I'll have fireside flipper speaker deck. There's a, I still help a little bit on speaker deck too. My friend owns it and runs it, but I still help once in a while I'll just keep track of those. And then I'll have a tags for the type of work I'm doing.'cause I can only do so much admin in a week. It's four, three to five hours. That's all I can handle of filling out. Employment I nines, or onboarding somebody or hiring or any of that kind of stuff. There's only so much you can do without, as if you truly love development there's only so much you can do with that. So I try to keep large blocks of time where I can do coding and then I try to shuffle the admin stuff around that. And then I always stack similar things. So I have two calls today. You guys are one call and then I have a call at two for a CDN to talk to them about some stuff for Box Out and for Fireside. And so I can a lot of it I can standardize and then work across all of them at the same time.'cause it's we wanna do some CDN stuff for Box Out, we wanna do some CDN stuff for Fireside. I can have one meeting with A CDN and I can talk with them. And I can cover both of those use cases. And that saves me, the lead up time to the meeting and the time after the meeting where I'm catching back up again and stuff. And it's a two for one. So I try to co collapse, condense. I try to keep track of my time so that I know am I being true to what I said I was gonna do. Both to myself and to my partners in each of the projects. And then I used to do is to get everything outta my head so I'm not stressed out. I would say that's, those are kinda like my main overarching systems and then there's little things, that I could probably go into too, but that's probably the big biggest stuff.
Ryan:Yeah. That's awesome. I'm curious as a developer, I often find that, depending on the problem, I need a chunk of time, right? That's more than it, everyone says time box, everything in your calendar. And if you're in sales, it's a lot easier to do than I think a developer. Although, maybe it depends on what you're developing. So with the different, time blocking that you're doing, are you saying, is a situation where on Monday I'm gonna do six hours on box out, working on this one problem, and then, the next day you switch to a different company and work on a different problem? Or do you try to do a little bit of each company each day? What does the, like the intersection look like? For lack of a better way of saying that.
John:Yeah, so I, the way it looks for me, it's I think it would be a little hairy. Like I think if most people watch me work, they would feel very stressed out. At the end of the day, I. Because I will sometimes I don't even change the timer. Like I'll have the test running here on, one thing or I'll be deploying on one thing and I'll just immediately switch and start working on a totally different app and project and company. And then I'll see, oh, okay. I come back. And so I will bounce around a lot. So like Garrett, who I work with, he does weeks on box out and two weeks on Flipper. And so there'll be slight, he'll answer questions here and there on. Depending on the week and stuff like that, but he's a very strict he splits it up and he focuses on one thing very deeply. For a long time. I just can't, I can't do that. Not because of my like personality, but just because of my roles in the companies. It's just not possible. I do Support for Fireside, so when a support request comes in, I'm gonna try and answer it. Because that's one thing that I can do to make a difference. When on Box out, I don't do support, so I don't have to worry about that. On Box Out. I might be the person who's like, okay, we have this people need, so who are we gonna hire? So I might be like, okay, look at my Rolodex of people and be like who could work for this? Who's looking for either, fractional or full-time and things like that. So it's, it just depends on. The various tasks and stuff like that. But yeah, I would say overall like it, it definitely helps. Um, Bounce around a lot. I do sometimes feel scrambled at the end of the day, and I wish that I could just work on one thing. There's also times where sometimes I get a chunk of work and I just work on one thing for, three hours and it's amazing and that's when I feel the most productive and the most happy. But the reality is because there are things, box out, I need to do PR reviews. I need to unstick people who get stuck on, crappy code I wrote five years ago. That kind of stuff. On Fireside it's different and so it just goes back and forth and there's not really a. A perfect way to say, on this day I do this thing.
Ryan:Sure.
John:I mean I, we had a box out weekly meeting from 10 30 to usually 10 30 to noon. We started an hour early.'cause we were doing this branding exercise. So we did that. There's a spot at which people were talking about like something, and I was like. I actually don't care what they decide here, like they're talking, but this is not something that needs to involve me, and so I did a fireside support request during the meeting. I'm
Ryan:Sure.
John:it's just whatever makes sense in a way that like isn't offensive to anybody else and gets the job done. So it's a lot of bouncing around.
Ryan:That, that's actually to hear your approach and how you do it is actually a bit of a relief, right? Because I feel I, I think almost everything you said I felt deeply I'm most happy if I could work on the problem I wanna work on for six hours straight. But the reality is there's other responsibilities that you have to take care of. The working on a support ticket during another call. That one. I feel I'm glad I'm not the only one.
John:It's rare. I try to give full focus to whatever I'm on, but there are times, like if people are just, let's say they're in a healthy way arguing about one thing back and forth, and I don't care about which way it goes, I can zone out. That's
Ryan:Yeah. Yeah. I.
John:But it's, yeah.
Ryan:We have a small team, right? We're a small company. There's only there's six of us now. Six of us, one, two. We get on a all hands once a week and sometimes we go down a rabbit hole of like sales stuff. And sales is not like I'm interested, like I'm a part owner in the company, so like I care right? But it's not, my business partner leads that. So he'll go into it with the salespeople and I'm like, I'm listening, I want to hear what you have to say, but I don't have a ton to contribute, so I can sorta drift off and everyone seems generally okay with that. I don't, like you said you don't wanna be disrespectful, but as long as everyone knows who you are and you communicated, I don't think it's really that big a deal.
John:I think the biggest thing for being scattered, but not feeling crazy at the end of the day of of switching between a lot of projects and stuff like that. The best thing is tracking your time.'cause if you track your time at the end of the day where you feel scattered, you can look and be like, I worked the whole day. I did the things that came up and I got things done. I did a lot of stuff. You don't have to track your time, but write down the things you do on a notepad beside you. Write all the things you do because if you can look back at the end of the day where you're like, oh my gosh, I don't even know what I did that day because I did 20 different tasks for three different companies. But at the end, if you can look and you can say I had whatever, I had six hours, and it was. Split up between these 30 things or whatever, like you can at least look and say, okay, I was productive. Like it's made me way happier. That's the only change is I spend a little bit of time tracking my time, but I feel way happier because I'm like, even if I feel scattered and like I'm behind on eight different tasks and people are blocked on me, I know that I did the best I could that day and so I feel better at night.
Ryan:We, we introduced something we call the daily huddle which is not like a standup, but at the end of the day we have a chat channel that everyone just posts what they accomplish that day. And it serves a couple different, we're a fully remote team, so you know, from me and my business project perspective, we can track what people are working on without having to. Their day. But that sort of serves the same purpose. We can celebrate wins. We can, raise blockers. We can say, Hey, did you think about X, Y, Z? And that's been a, I think, a big part of our remote process. I think. I use a, a timer like I forget what you said. Yours was called a toggle.
John:Toggle.
Ryan:Is that yours? I, mine's like a Apple plugin, but it basically just says, Hey, I, I hit go. I go for an hour. At the end of the hour, I stand up for five seconds and sit right back down and start again. But it helps me. That just coming up for air at the end of that each hour allows me to look back at my, this is what I said I was gonna accomplish today, right? Am I doing it? Do I need to switch gears and go to the next thing? Like it, it forces me to say, all right, don't get sucked into that problem. What do you used to call it? Nerd Snipe.
John:Yeah.
Ryan:like don't get, don't do it. I know you want to, but you gotta really go take care of this other thing and, get your teammate on blocked or whatever it may be. Yeah, I think that's all great advice.
John:Another really good one is Mac Break. Z is what it's called ma, MAC break, and then a Z at the end. And they will actually do like micro stops where it'll be like based on keyboard activity or mouse activity. It'll be like, you need to take a break for 20 seconds. just breathe deeply, look far away, and then come back and you can change all the settings to be, and it'll give you stretches every five, five minutes of stretches every 50 minutes or whatever you wanna do. I found that really useful when I was having a lot of hand and whatever, eye issues and stuff like that yeah.
Ryan:Yeah, especially prevalent when you're doing something you don't really want to do, but it has to get done right, like when the focus is stretched thin.
Brendan:Yeah, I use an app that sounds similar to the one you just described there. It's. probably more like what you got too, Ryan called session. I Like a Pomodoro I always said it to the max too. I'm like, okay, I'm just gonna set this to 55 minutes. Like even though the default's 25 or whatever. But I think the similar to what you were saying, like this does let me choose what am I working on so I could set an hour to do one thing. And
John:Yeah.
Brendan:as many companies like you do, but it is still nice at the end of the day what you were saying to be able to look at that and say, oh, okay, I actually work for whatever on each of these problems. And. it is a nice just a refresh for your brain to be like, yep, I did some stuff. This today.
John:very easy if you just it doesn't, even if you're just in one company, like you can feel scattered at the end of the day. Like it's very easy. It doesn't, the number of companies I think is immaterial and that's, I think, the thing, it's not impressive that I'm in like two companies or have three products or four products that I work on because I. The, each of them have like Box out has, I don't know, 10, 15 different people that touch some part of the entire company process of, making the sausage. And, even on Fireside there's at least three of us that are pretty active. Maybe even four or five. We have a couple contractors that do various things. So it's I have a bunch of people helping on with a lot of different shape of problems and stuff like that. So it's very easy. It is a lot easier to bounce around. And but again, at the end of the day, it's just, do you feel crazy or not? And that's the goal is don't feel crazy. You want to have some log of what did you do so that you know you're productive? And sometimes I literally I'm okay with the fact that like I just sat and I read something, that was not beneficial in any way to any company or thing, but I learned a thing and it was fun, or I enjoyed myself, or I do a lunch and I'll go two hours and I don't care. That kind of stuff too, but.
Ryan:I think that's good perspective. It really doesn't matter the number of products, right?'cause the, it is just how you slice and dice your day, right? It's whatever's important to you. And may, maybe let's bring it back to rails a little bit, right? We talked about how AI improves your productivity. How does Rails help you with the business side of things? So I think it's well known that Rails is a, as a framework, is good for developer productivity. It helps you shit faster, has all the tooling. You don't have to think, you don't have to get down in the weeds. Is there anything that stands out to you that crosses the chasm into the business or strategy that Rails provides that I didn't already mention? It's a deep question. I.
John:Yeah, that is a deep question. I think, for me it's probably. Cheesy answer or like the easy one, but it's like I know it so well. I know like most of the time at this point, in my life I've been doing this for 20 years with various databases. I've probably used four or five different databases. I've probably used four or five different frameworks, languages, all that kind of stuff. And so I'm like, at the end, I know exactly how to build something, but you still have to go and build it. And so I want that process of actually building it to be the least amount of friction. So I think that's one thing that's like why I stay with Rails is because it's the least amount of friction. It's like you wanna get your model in your data, like all that kind of stuff. You wanna route some stuff to it and then you wanna show something to the user. So I like that part of it. The other thing for me that I keep coming back to is just the beauty of Ruby. That's that's just it for me. It doesn't, I see a lot of heads nodding. For those that are not watching a video feed, it's just, it's, Ruby is so beautiful to read. It's possible to write really bad Ruby. I've seen that but I think most of the time, yeah. But like most of the time it's very clean. It's possible to be very expressive, very clean. And that's what I love.'cause I, when I look at even just things like TypeScript or Java or like other things like that, and you have like public static, void, final, whatever, and you're just like, it's just all this extra stuff. You gotta say even Ruby, it's just just say private here and then just. Define a bunch of things after it. You can say private deaf, you can do that, you don't have to, like it's just little things like that I think are just what have added up that make me, it makes me more productive.'cause I think faster you can read something into your head and load it in and then be productive with it, the better. And that's your, your advantage. Box out's been one or two devs for a long time. We now have more, but we went well past seven figures. Almost all the way probably to almost 2 million a year just with two devs and not two devs cranking 80 hours a week, two devs like, camping for a month in the summer together with their families and stuff. that kind of productivity I, I just haven't found anywhere else. So that's what I keep coming back to.
Brendan:A follow on to that with all these different apps. Do you use the same front end framework?'cause obviously you
John:Yes.
Brendan:on the front or you could stick with the rail stuff. But what Flavor and are you consistent across all these different apps?
John:Yeah. So consistency is very important, and it's more important to me than individual, like preference or productivity. So for everything that. When I'm involved I, everything I do is for the productivity across everything that I'm on. For example, like every fireside flipper, cloud speaker, deck, box out, all use bootstrap. It's all within four or five, they're almost all the same. And and again, it's do I like bootstrap the most? I don't know. I don't care. Am I able to get the thing done with Bootstrap? I am. And it's the same on all of them. So when I go from Fireside to box out, I'm not like, okay, now what's the name of this tailwind class? Or what's the name of this? Or I don't get too far behind. Here's Bootstrap, six, and here's Bootstrap two. And so they're totally different. And then you're basically in the same scenario. We try to keep things similar and then even the same with Rails versions. We try and stay right now we're trying to stay all in the kind of the sevens. And so that means, nobody's gonna be on the eights right away. That's okay though, like we did, but we standardize it. So the only one that has React is box out. And do I like it? No, I don't. But it makes it so that the people who are doing spots that I'm not touching they like it. And so I'm like, okay, I just, I'm okay with that. On Flipper and on Fireside, firesides so old, it still has jQuery. There's, and flipper, flipper's got, some stimulus. It's got maybe like a tiny bit of view. There's just some random smattering of things. But overall, yeah, we standardize very hard. Even, to the chagrin of an individual, it's not about the individual productivity, it's not about the company productivity, it's about the multi-company like productivity of going across many different apps, trying to standardize as much as possible.
Brendan:Yeah, that makes sense.
Ryan:I think I mentioned this to you in a prior conversation, but I'm a big fan of box out how did that come about? I am, I've just been, I always thought that was a great idea, like right from the get go. I, I, think I first saw it many years ago and you know, I, when I discovered it was you were involved with it, I was like, no way.
John:It was not me. I thought it was a stupid idea. So I just wanna, I wanna put that right out there. You don't always have to be right to still make money on something. So I thought it was I, when I remember when they told me what they were gonna do.'cause we all knew each other. Like it was Robbie's idea. Robbie was a sports information director and he was all of a sudden having to do social media posts. And he's I don't have time. I'm spending 30 minutes after the game and while I'm trying to make this graphic, the local news team has tweeted it and everybody's retweeting theirs. And then they never even see my pretty graphic. He's it's just too slow. He's we gotta, yeah, I gotta do something that's faster. So he started talking to his friend who's a designer, Jeff, who's okay, let's try and get like some templates so that people can just kinda get a Photoshop template, open it up, tweak the thing, and then ship the graphic, and then they started talking to Steve. So Steve. Is Robbie's. So he's been my business partner off. Steve has been my business partner off and on back at ordered list. We work together at GitHub and now at Box Out, again Flipper, all the stuff we're together on. But Steve is also the, he's married to Robbie's cousin and so they, so Robbie and Steve knew each other from that. We all went the same school, varying years apart so that we were familiar with each other and stuff. So they were like, Hey Steve, can we build this in software? And he was like, yeah, sure. Like I'll just do you a solid. Make it cheap and give you something that you can see if it'll work or not. And Robbie went out and sold 40,000 before it was even done. And Steve was like, ah, let's, how about I not charge you and I'll just be an owner with you? And they, and they built that while Steve was still at GitHub just on the side. And then at some point, he left and did it on his own. And then a couple years later, it was when I left, so I think he was maybe five years at GitHub. I was like seven. So it was not my idea at all. I take no credit. When they were telling me what they were gonna build, I was like, good for you. And then, to myself, I'm like, who's gonna pay for that? That makes no sense. I was horribly wrong and, paid the price ultimately when I bought in, in 2019. Yeah so no credit to me at all. But it's a, it is
Ryan:I appreciate your candor. I like I like the concept. I've always been fascinated by it. I feel like there's other applications or other industries that could use the same thing and I. It's always been in the back of my head. Maybe I can do something that emulates what they're doing in the sports field. Of course I've got my hands full with other things right now, but maybe we'll get back to it at some point. And maybe you guys are planning on going to expand. I don't know. Like I'm not trying to steal your thunder here either.
John:You can steal thunder. That's okay. We're way ahead of you in templates and texts, so it's fine.
Ryan:There's no
John:I'm just
Ryan:chance of me catching up for sure.
John:but no, but it's. Yes, it's definitely, that's a real thing.'cause just a template library to build up, three, 400 templates, it just takes, it takes a long time. But I actually think you're totally right. I definitely, we've been working very hard on generic sizing everything. So like our graphics, so like when you create a graphic, you don't have to, it like, it looks initially like sports, but you can put non-sports in. We have social media agencies using it for restaurants, for schools, for. All kinds of different things. And so I feel like that would be a big vertical. Any vertical where time matters is what I think that's where you want to hit. If it's I wanna be creative or I wanna do Canva or Photoshop or things like that and we have competitors in the sports space and like they're literally just recreating Photoshop in the browser with pre-made templates and we're like, that doesn't make any sense. The point is speed. The point is to like, this graphic's gonna be seen for four seconds, don't spend 30 minutes on it, spend four or two or less, like we're getting now, to the point where like we just added the events feature. And it's literally is just like an iCal sync of your schedule. We pull it in, we automatically use, Jaro Winkler or Levenshtein or something to try and figure out your opponents and match them up with, and our opponent database has logos and colors and so it'll bring that into the graphic and it'll do all this stuff where you just give us an event and we'll make an entire graphic for you and you don't have to do anything. We'll schedule it out X days ahead to go out. Like all that kinda stuff. It's the whole goal is like no effort. Yeah, but I think there's other stuff like op, like Banner Bear does open graph images. I'm like, we could totally do that. There's
Ryan:Yep.
John:of, any place you need custom template generation where time is important. I feel like even fireside, I'm like
Ryan:You guys have an API.
John:not yet, but that's one of the things I wanna
Ryan:Okay.
John:that I wanna work on this year is building an API so that we
Ryan:I'm gonna reach out to you separately.
John:yeah, do it. I want podcast templates. I don't want you to
Ryan:Yeah.
John:Do any work to make like your first podcast cover art, like you should be able to just upload text and a logo and maybe a photo and it, we do automatic cutouts, p and gs with Box out. We do all kinds of cool stuff like that, so I'm like, yeah, it makes sense
Ryan:My company Locable is like a marketing platform for a Chamber of Commerce or Main Street or a local publication. And the big thing is events and most events don't have a picture, but if the event doesn't have a picture, it doesn't really. Get shared. If we could make it like easy to automatically generate something to go with that event. Our whole mantra is make it easy, pe make it so that these people can do marketing in 15 minutes or less. Every day consistently. Just move the needle. So that's stuff I, that's why I asked if you had an a PII was like, brain's moving.
John:That's the plan. The plan is to basically have some kind of an API. Move to be, not move to be platform based because like we need, like we have tons of customers, we're gonna keep serving them,
Ryan:Sure.
John:love to have a platform option.'cause we've had a ton of people come in and try to buy us and we're like, no.
Ryan:Yeah.
John:it would, it it doesn't, we're doing fine and we're bootstrapped, so we're not in the same situation. We don't need liquidity, we don't need, like that kind of stuff. So it doesn't really work. So I'm like, what we want though is we wanna build like this platform so people can just. Even make their own templates to use and things like that. I think that will probably happen over the course of this year. But I, yeah, I can't promise it, but I think it'll be really
Ryan:We won't hold you to it.
John:previews. Yes. You heard it. Yeah. It's new scoop. It's funny.
Brendan:Oh, this has been great. Yeah.
Ryan:To call it a day. Appreciate you, you coming on. Anything, any last things you'd like to share? Where can people find you? Anything you're promoting these days?
John:jnunemaker pretty much everywhere. Don't try and spell it. It's easy, but nobody gets it right the first time. So just look in the show notes and you can pretty much find me anywhere if you wanna follow any of this kind of stuff.
Brendan:Cool. Thanks again for joining. It's been great.
John:Thank you.
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