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
Jason Swett is Back to Discuss Sin City Ruby and more
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
The hosts welcome back Jason Swett to the podcast. He discusses the recent Sin City Ruby conference, including notable highlights such as having Dave Thomas as the keynote speaker. Jason provides insights into the conference's history, the challenges of organizing events in Las Vegas and the financial factors leading to the decision to discontinue Sin City Ruby. Other topics covered include Jason's personal perspective on balancing multiple professional commitments, and some Docker debugging.
00:00 Welcome Back, Jason!
00:09 Sin City Ruby Recap
01:22 Dave Thomas: The Keynote Surprise
03:08 Conference Highlights and Extracurriculars
04:34 Challenges and Future of the Conference
11:13 New Beginnings: Jason's Career Shift
18:36 Improving Developer Onboarding
22:08 Challenges with Docker and Testing
24:12 Exploring Docker Configuration Issues
29:22 Balancing Multiple Projects and Burnout
32:26 Deciding What to Cut
35:48 The Value of Podcasting and Networking
37:16 Conclusion and Final Thoughts
Links:
All right. We got Jason swept back with us on the podcast, our first returning guest. Welcome back Jason. Good to have you.
Jason:Hey, good to be here.
Brendan:So you just had Sin City Ruby a couple weeks ago, and uh, and I did not get to attend, but thought it'd be good to just check in and see how that went from your perspective being the last one and everything. Yeah how was it?
Jason:Yeah, it was really nice. It felt somewhat similar to last year. For context, we've done it three times. The first year it was slapped together'cause it was actually meant to be a small class the first time I did it, but nobody bought tickets. So I'm like, how do I salvage this thing? And I turned it into a conference and it was a tiny conference with 40 people. Then the second time we did it. So the first one was 2022, second one was 2024. And the one we did in 2024 was a bit bigger than the first one. And then this one was just slightly bigger than the second one. I thought that in 2024 we had 80 people, but my wife told me I had the numbers wrong. I think it was maybe more like 60 people, 60 or 70 or something like that. and then this one was like 70 or 80 in that neighborhood. So size wise, it felt similar to last year. And we had an interesting development right at the 11th hour. I happened to talk with Dave Thomas, the author of the Pragmatic Programmer. emailed me out of the blue and said, Hey, can I come on your podcast? And I said, of course. then after we talked just on a whim after the recording, I asked him if he'd like to speak at Sun Ruby, and he said yes. And so he became the keynote speaker. So we all got to meet Dave Thomas.
Ryan:That's exciting. What was his talk on?
Jason:It was about various different programming languages. It, the title was something like languages love Story or something like that. I'm sure I'm getting that. Very wrong. But he like went way back into his history 'cause he's been programming for like over 50 years. And so he described all these like esoteric languages that none of us have ever heard of and stuff like that. he ended with Ruby and I think said something to the effect that Ruby is his favorite language. And he said I'm not just saying this to pander to everyone here. Like it really is my favorite language. So that was really cool to see. And it was interesting. He gave the whole talk with no shoes on.
Ryan:Okay. Just for fun.
Jason:I don't know. It's, I
Ryan:Yeah.
Jason:of his little eccentricities.
Ryan:Love it.
Jason:Yeah. Yeah. But that was really cool. And I brought my copy of the Pragmatic programmer and got it signed by him, which he graciously did.
Ryan:That's fun. And let's see. Are there any other highlights? What were the extracurriculars this year? I know you always try to organize something on the side. Was there an event or?
Brendan:as my first question?
Jason:yeah.
Ryan:Oh.
Jason:So there was arm wrestling. Again for context, we had arm wrestling in 2024. There were like three or four matches, but I. At this time I did it a little bit smarter and I passed around a signup sheet. So we had 10 or 12 people who signed up and we did a tournament style. myself got eliminated in the first round and then yeah, there was, there's quite a lot of arm wrestling, so I was pretty cool. And then extracurriculars, somebody arranged karaoke The last night of the conference. and that was pretty fun.
Ryan:did you get up and sing?
Jason:I did,
Ryan:Okay. What was your song?
Jason:I did a couple, I did Smashing Pumpkins "Zero", and then I did train in Vain by the Clash.
Ryan:Nice.
Jason:then after that I did a duet with guy from the conference we sang. Wanna Dance with Somebody by Whitney Houston.
Ryan:That's a, that's an interesting one.
Jason:Yeah, and that was later in the night. So we really cut loose and we
Ryan:I.
Jason:dancing together on, not dancing together, but like dancing as part of our act. It was pretty cool.
Brendan:That's fun. Yeah. And this was a new venue too, right? You were at the MGM,
Jason:it was at the MGM Grand which was a great. Place to have it. I didn't know this, but the MGM Grand is just absolutely huge. So there's tons of restaurants and tons of, they have a pool just like everything you could want is right there. it was great that way. The downside is that it was really expensive. The first two times we had it at the Tropicana, which was pretty affordable. We tried as hard as we could to find the most affordable place we could, but the MGM was like the least expensive thing we could find. And it was like we had a certain idea of how much it would cost, but that kept kept being like hidden surprises and so it ended up costing quite a lot. And ticket sales were not quite what we hoped and expected. And so that was a big part of the, that was the basically sole factor in deciding not to do it anymore is that we're just gonna have such a big financial loss for this conference. But I should mention that some of the speakers and attendees did something very kind. They organized an ad hoc auction and they auctioned off some. Some items and services and stuff like that. For example, Dave Thomas auctioned off an hour of his time. Other people did a similar thing. You could get a consultation with Chris Oliver, for example. So that was really nice and it helped soften the blow a little.
Brendan:That's
Ryan:That's awesome. Ne next time you have an auction like that, you gotta spread the word. I know it was impromptu, but I would I would pay money for a consultation with either of those two people.
Jason:Oh yeah. Yeah. Yeah, so it was really nice bittersweet since it was the last one. And I've told people I'm not necessarily done with events in general, just done with Sun City Ruby.'cause the thing is if you want to do a conference in Las Vegas on the strip at a hotel, like it's gonna be expensive. We could theoretically do something like off strip, it's at that point, I dunno, kinda what is, why are we doing the whole thing,
Ryan:what about Old Vegas, like the old downtown? Like I don't know if there's any conference things down there, but I know that it's fun to go out down there. There's a lot to do with it. It's not quite as crazy either.
Jason:So actually one of our speakers and a friend of mine, a freedom al. He is from Las Vegas he mentioned to us that we could probably do something affordably in Old Vegas. and so that's an option that's available to us. But there's also the factor of do we want to keep organizing this conference that happens like 2000 miles away from where we live?
Ryan:Right.
Jason:Yeah, me and my family, we live in Michigan, so it's like a big four hour flight to Las Vegas. and it started, there's a whole long story, but it started in Las Vegas through happenstance. It wasn't like, it wasn't like we sought that out specifically. And I don't know, kind of after I made the decision or we made the decision not to do it anymore, it it's gonna take a little more to like, back the idea of making that attractive to do again.
Ryan:Sure.
Jason:Yeah. So not sure. I don't want to completely rule it out, but right now I'm not leaning in that direction.
Ryan:Set.
Brendan:the Midwest as well, I'm definitely open to a more centralized conference so that I can go to it more regularly
Jason:Yeah. And what I'm thinking, me and my wife still have to like align on all this, but what I'm thinking personally is there's some really nice spots in northern Michigan on the lake. And it could be a cool partly outdoor experience at least I don't know if that's the way to put it, but somebody, when I was talking at the ca at the conference they said oh, maybe you could like have a lodge or cabin or something like that in Michigan. I'm like, yeah that's like kind of what I was thinking about. So something along those lines is what I'm like vaguely. brewing in my mind. I think that could be really nice.
Brendan:Yeah, we'll definitely keep us posted'cause I'd be interested for sure.
Jason:Yeah. For you, that's a really close trip. I was gonna say flight, but maybe you'd even drive. But then you gotta drive around that lake.
Brendan:Yep, exactly.
Jason:I.
Brendan:But it's still closer than Vegas and that's the key for me.
Jason:Yeah. yeah. And it would be a totally different thing because, okay, here's the other thing about Vegas. I don't think it really has a local draw. There's maybe three or four people who came to it this year who were local. And I think there was one person who came from Reno, but other than that, like there's not really a Las Vegas region, even in Las Vegas itself, like it's not really a tech, it's not a tech hub. Even though there's a lot of tech conferences there it's not a tech hub.
Brendan:Conference hub at best.
Jason:yeah, exactly. And so if we did something in Michigan that would have a more of a local draw, surely a lot of people would come from Michigan and the surrounding states.
Ryan:That's 50% closer for me, so I'll take it.
Jason:Yeah, I think that would be like a two hour flight to get Michigan.
Ryan:Yeah, it wouldn't be too bad.
Jason:Yeah. The only trouble. Is and I don't know how much this would deter people, but you can't just get a direct flight like to, Rapids where I live, or Traverse City, which is another like candidate for where it might happen. So you'd have to fly like to Detroit or Chicago and then take a, take another flight to the smaller town. But I don't know if that's, I don't know if that deters people or not.
Ryan:It's not gonna deter me 'cause I pretty much have to connect to go most places because I'm pretty rural up here. But it.
Brendan:to go to Vegas,
Ryan:that the idea of outdoors on the lake is appealing.'cause I can bring the family and let them, make it a vacation. And not that I couldn't bring them to Vegas, but my kids are little, I probably just, it's not worth it. But if there's outdoor activities and it's hopefully summertime or at least a nice time of year that makes a big difference too.
Jason:Yeah. And for everybody, Las Vegas is a totally wallet draining experience, and so the idea of having it somewhere more affordable is appealing to me.
Ryan:Yeah. Maybe this is a good time to segue, given that you're closing one chapter with Sin City Ruby, and you're not sure I. What's in store for you in the future, but you just started a new role. Do you wanna tell us a little bit about where you're working now and what you're doing there?
Jason:Yeah. Yeah. And I'll give a little background on what led up to this. So I was working at a full-time job from end of 2022 near the end of 2023. And then I went full-time on consulting and that was like a feeling my way through the dark kind of experience. I. I, I started off, both you guys are former consulting clients. I started off working with very small software businesses where it's just one to three people. usually where the CTO is the only programmer. then I started working with bigger and bigger organizations. The last client that I wrapped up with had 50 or 60 engineers. And the nature of the work kept changing. And every time people would ask me like what kind of consulting do you do? I'm like it's like different month to month client to client. I kept waiting for a pattern to emerge and no pattern did emerge. And that was all fine, as long as things kept advancing, or at least kept going. But then eventually things stopped going. my, my last client engagement ended and I didn't have anything else. And I'm like, okay, I need to get something else 'cause I need to have an income. But nobody understands what I do. And so it's can either try to find a new consulting client which is like a big roll the dice.'cause it's like I could get a new client tomorrow or it might be six months before I get a new client. And that's, that just seemed like a really big risk, like an unacceptably large risk. And so I'm like I could get a job instead. And that's probably a safer bet to try to do that. And something else that was different from when I started consulting was I started a product business, this CI platform called Saturn CI that I've talked about on this show before. So it's like I'm a believer in having as few irons in the fire as possible. if you try to do too many different things, you're gonna spread yourself too thin and not be successful with any of them. And so I'm like, okay, maybe what I want to do now is have a job and then in parallel to that, work on my product business. the, that way I can turn off that part of my brain and just get a steady paycheck and have that part stable.'cause that's another thing, like have unstable thing, it's if you have multiple unstable things going on at a time, that's a lot trickier. So if I can have the one stable thing and have the other volatile thing that I don't depend on, then that's a bit better. So all those things like led to a decision to, to get a job, it's, it took me a bit of time. Like it took me from the beginning of January to the end of March. To finally get something. But I did finally get something and so now I'm working at a place called Cisco Meraki and Alan Ridlehoover and Fito von Zastrow from Cisco Meraki have been pretty active in the Ruby community lately. I. So a good chance that a lot of people have heard of Cisco Meraki by now. I started there on March 31st, I believe it was. So I've been there about weeks as of this recording coming up on a month, I.
Ryan:And what is your new role there?
Jason:Yeah, so they have a new team where they're working on their build and deploy pipeline, and I'm the tech lead on that team. I started, I was the only member of the team. we have another guy and we're hiring some other people. But yeah I'm I'm on this new team.
Ryan:That's exciting.
Brendan:does that mean you're gonna be, you're like involved in hiring these people or that's outside of your role?
Jason:don't know how involved I'm gonna be in that. I'm involved to the degree that I already referred somebody and they're in the interview process, but I don't know if I'm gonna be involved any more than that.
Brendan:Got it.
Ryan:So you said you've been in the role for approximately three weeks. When you start something new like this, how do you go about getting yourself up to speed and not necessarily just in, the code base and the infrastructure, but just in the role and in the company as well. Do you have a process you follow, or a framework or any kind of strategy?
Jason:A little bit, maybe not a very conscious process that I've articulated yet. In this case, my first week was all training. It's a big company and they have a pretty established training procedure. So the first week was all that. Second week was Sin City, Ruby. And so
Ryan:Right.
Jason:week was really my first real week. My new boss suggested various people who I go and talk to. And so I talked with some of them and as I encountered other people, I'm like, Hey maybe we should get to know each other. Let's have a call and acquainted and you can hopefully teach me some stuff and stuff like that. So I've been doing that and I've been learning a lot from people. In this case it's very different from the past because it's just such a huge organization. Cisco Meraki has 2000 developers. so it's just a scale that I haven't seen before. Not even close. But I like it. There's always stuff going on. if you log into Slack, there's, there's a constant stream of messages and there's constantly stuff happening. So there's a lot to go off of in terms of answering the question of what is the picture here? What's happening?'cause there's always activity and there's a whole bunch of history. there's a whole bunch of documentation, so there's a lot to dig into, unlike a really small company where it's I don't know. I've had situations before where it's like I'm working on a really small team. Most of the knowledge is in the heads of these, like two people. Because they're like the most senior, they're the most important, they're the most busy. So the only way for me to really learn anything is to to take up time of these super busy people. And so that makes the onboarding process kind of tough. So this is luckily not like that. It's a bit easier to get the picture. The flip side of that is there's so much stuff And it's hard to. To see the forest for the trees and all that. Yeah,
Ryan:if.
Jason:not a very specific process. Just I think the main thing is like talking to people and seeing what the people there could teach me.
Ryan:That makes sense. Quick tangent, if you'll allow me what would you suggest to smaller companies the situation you just described where all the knowledge is locked up in a couple of senior people, like what would you suggest to them to make onboarding? A better experience for new developers. What could we do now? And I say we, because I feel like you, you probably just described my, my company to some extent, or at least that's how I'm feeling, but, so what could we do to improve the developer experience specifically to make onboarding new team members? Better or easier, or whatever word you want to use to describe that scenario.
Jason:Yeah, interesting question. I don't really feel qualified to give a very complete answer, but I can say a few things because there's certain things you can do that I know are a good idea anyway. Like it's probably never premature to make your development environment as automated and easy to set up as possible.'cause even for one individual, like if you get a new computer and you have to switch, it's nice to have everything really portable. So you can just get set up with a single command or as close to that as you can get.
Ryan:So is that Docker for you?
Jason:yeah.
Ryan:Yeah. Okay.
Jason:Yep. And then this is a whole different can of worms, but making the product. very what's the word? Cohesive, coherent self-explanatory, simple, all those things. Obviously all that is much easier said than done. But imagine that you get hired to work on Basecamp, even if
Ryan:I.
Jason:worked with the Basecamp product before. pretty simple and intuitive and stuff like that. But if you get to, if you get hired to work on I always pick on CircleCI if you were to get hired to work on their product. It's like conceptually it's a nightmare. Like I've been using it for over 10 years and I hard, I like still get confused every time I use it. And so to work on something like that where it's like kind of conceptually incoherent, gonna make everything harder. And so I can't say everything about what's gonna make onboarding easier for people, but I know that making your product simple and coherent and conceptually sound and all that stuff, never gonna wish you hadn't done that. So I can confidently say that's a good idea no matter how much it may or may not help with onboarding. But obviously it's self-evident that it would help at least some
Ryan:Sure. Yeah. We you obviously helped me set up dock for our app way back when, but that had a huge impact on. Onboarding, it used to be that, the first test of any contract or employment work with us would be, can you get our app running? And that wasn't always a given. And it could take days or weeks for some, I. People to get it going. Now we have some very old dependencies that are actually quite difficult to install. So I'm not saying that this was like, any fault of the developer. But now with Docker, we've gone from what could have been days or even a week to hours and or less in, in some cases. In, in most cases you just build the container and you're off and running, which is nice. But another tangent. And this is I think right up your sort of testing alley is, for some reason with Docker, our test suite has become like incredibly slow, like way slower than running locally. And I think that is, related to the number of system tests we have and the fact that there is some sort of overhead with Docker connecting and communicating with the local host. Um.
Jason:Hunch is I wonder if the resources allocated. To the Docker machine are too small.
Ryan:I wouldn't even know where to look at that. Is that just the is that a Docker configuration within like the Docker file
Jason:well there's two layers to it. There's Docker desktop, and that kind of sets the global maximum for what resources can be allocated to Docker in general. And then in your Docker compose file for a specific project you can set like how much RAM it's allowed to use and stuff That.
Ryan:I'll have to look into that because that's like becoming a, I'm really trying to keep up, the Docker configuration and keep it current so that, we solve this onboarding problem. But testing is becoming, it's so slow now. Like the test suite, if I run the whole thing is like eight minutes when I run it locally, which I'd like it to be shorter than that, but. Coming from having no test to where I am now, like eight minutes is a bonus on Docker. It's taking 45. That's a huge spread. And I'm digging into why that is. Like I, but so far I'm coming up empty.
Jason:Okay, so something's really wrong.
Ryan:Yeah.
Jason:Interesting.
Ryan:And it wasn't always like this, I don't know what I don't know here. And maybe since you set this up, maybe you have an opinion. But the way we set up the system test to work with Capybara is that it was using Chrome on local host and. Trying to update that so that it uses the Chrome driver in the container. And that's what seems to be introducing the slowness. And that seems backwards to me. I feel like it should have sped things up, but it's going the opposite direction.
Jason:So you're going from having the docker container, use the browser on the host machine to having the docker container. Use a Chrome instance in a different Docker container.
Ryan:So the let me see if I can just rephrase this. I was distracted by the frozen screen. The original setup was, I would run Chrome driver, in a terminal on local host, whether that was running my local test suite or the Docker container, and we just had that in Docker. It just connected to the remote URL on the local machine. With the latest version. Now that we're upgrading our app and we're at a more current version of Ruby and Rails, I'm trying to rely on the web driver's gem to just grab a. And the Chrome driver and not have to rely on this external dependency, which is I have to install Chrome driver and have it running in a terminal. And I made those changes locally and everything was working. And it is actually, I had some speed improvements. Then I went and tried to apply the same changes to Docker. And what happened was a, I couldn't get. It to run inside the container. So then I was like, all right, let's just go back to the old way. I was doing it where I was, giving Capybara the remote URL, and then running it, the Chrome driver on my local host machine in a terminal as a separate process. Now, as far as I can tell, everything else is the same. Other than that, and now it's like I can't, the test suite is so slow that it's, it's almost unusable, right? I can't wait 45. It's faster to just look at ci, which runs in eight minutes.
Jason:Yeah.
Ryan:So I don't know what else I did and I'm not necessarily asking for an answer 'cause you, it's impossible without looking at the code. But if.
Jason:I can share one thing real quick. I don't understand everything about your scenario, but the way that I do it when I do it like that is to have one process running the rail server. Then another process running Chrome. So you can, in your Docker compose file, you can tell it to use a certain Chrome image from Docker hub. And so then it'll have one container running for your Rails app, another container running for Chrome and your Rails app can connect to the to the host. Name for that Chrome container?
Ryan:Okay.
Jason:you're doing it or are you doing it a different way?
Ryan:No, I. I think I was my, my understanding of how this works is not yet clear, so I think that's part of the problem. I am,
Brendan:sounds if you're open for some more consulting, Jason, you could Talk to Ryan offline.
Ryan:Yeah.
Jason:Yeah.
Ryan:But that's interesting. Let me, I'll, I'll check into the running a separate container for Chrome driver and then I'll report back and let me noodle on that and, maybe we can talk about that in the future episode.
Jason:Yeah. Yeah. I'll
Ryan:If any.
Jason:on that one container, one process is the convention with that. so I don't know if you're trying to use Chrome in the same container as another process, but I'll just share that little tip of one container, one process.
Ryan:Yeah, the. The original attempt was to let rails handle it, right?'cause web driver, if you put the web driver gem in there along with the browser driver, it's supposed to download and run. I think in the same. Processes rails. Maybe I have that wrong. When that, when I couldn't get that working, I then went back to the original setup, which was simply to run it on my local machine and have docker tunnel or whatever the correct words are. I basically connect to the local machine as a remote host to run it that way. And for whatever reason, that didn't work either, although it was working. Before, so something else had to change. Anyway, let's move on because I don't have the details that, that will make this a useful conversation.
Jason:And one very last comment, you can look at the Saturn code base on GitHub and look at the docker compose config there, and it might give you some clues.
Ryan:okay. Thank you.
Brendan:That might be a good segue. Really quick to. Obviously you're not consulting anymore, you are gonna work on Saturn CI still, but you also have a lot of other things going on, or you did, at least with when you were consulting. So there anything you wanna say about maybe what you're gonna do there, if you're gonna change things, maybe you haven't decided? Any thoughts there?
Jason:Yeah. So in my, career, I have all these parallel tracks of activities. and not all these tracks are always active at the same time, but there's blogging, podcasting, both my own podcast and going on other people's podcasts. I have a YouTube channel, I have an online meetup. used to host a conference as we talked about, Sometimes I speak at other conferences. Let's see, I think I said blogging. I also have a, an email newsletter and
Brendan:And your snail mail newsletter.
Jason:I have a snail mail newsletter. And let's see, and then I have Saturn ci, so that's a lot of stuff. And now that I have my new job and now that I'm not doing consulting anymore, it has prompted me to step back and say okay, am I doing? does it still make sense for me to be doing everything that I've, that I'm doing? Because I am just like so busy. And honestly, I'm feeling pretty burned out. Because my like, level of effort that I've been putting into everything and time and stuff it's been, it's felt out of proportion with the payback. And I think that's the definition of burnout is when you're working really hard in not seeing a reward or a prospect of a reward anytime soon and stuff like that. So I got all that stuff going on and then I got like personal projects too. Like I've told you guys that I'm doing some home remodel work and that's all going much more slowly than I would like it to. And so I have to like it. All the stuff is connected. That's why I mentioned that. Everything has to be taken into account when you're deciding what you can spend time on.
Brendan:Yeah, exactly. There's only so much time, right? No matter what.
Jason:Yeah. Yeah. So I gotta work in my job. not negotiable. So out of all this other stuff, like what am I gonna keep doing Saturn ci I'm not gonna quit doing that.'cause that is that is what I see as my retirement plan basically. And ideally my retirement plan starts being effective but that's not gonna be the case. Maybe the retirement plan becomes effective in five years or something like that. 20 years, whatever it is, I'm, it's still gonna be worth it.'cause I don't have any other retirement plan. so that's the thing. I'm not gonna quit that. And so what else? What are the other things and should I keep 'em or cut 'em? The other night I was like starting to make dinner I had to stop partway through because I had to go do the code with Jason Meetup, which I love doing. But I had to stop in the middle of dinner and I wasn't nearly as far along as I needed to be with dinner. And then I, as I was walking from my house to my office in a separate building in our property I'm like, do I absolutely have to do this? And I said, no I don't absolutely have to do this. I can cut it. And between my house and my office, I made the decision to stop doing it, which was not the first time it occurred to me, I kind of made that final decision at that point. And so in the call I told everybody, Hey, I think this is gonna be the last one. I think I might actually do one very last one, 'cause I want to email my email list and tell 'em, it feels appropriate to say, Hey. You still have one very last chance to come to one. Anyway, I'm gonna cut that. sad about that, but can't do everything. And so that leaves all this other stuff like blogging. I haven't really done blogging in a really long time. The email list, I think I I stop doing that, I think it's gonna have varied negative consequences or rather. The benefits that I get out of it will go away. So I don't think it would be a good idea to quit that.
Brendan:Plus he could probably use that for marketing at some point with Saturn ci, right?
Jason:Yeah. The snail mail programming newsletter, I'm a little bit more torn on that I really enjoy doing it and a lot of people have told me they really enjoy getting it. And it does make money. And so I'm really not sure about that one.'cause I could cut it, but it would really, that would really be painful to cut that.
Ryan:It feels like that's the unique thing that you're doing that no one else is doing. Like you have to do email, right? Like it's it's almost non-negotiable these days. If you're doing any sort of product, the snail mail really does set you apart.'cause I don't know anyone else who does that.
Jason:Yeah. Yeah, and it's a good way to keep in touch with people. There's people who I hadn't talked with for maybe five or 10 years. I like went through my list of people I know and I called some people and I'm like, Hey, I'm doing this weird thing. Can I send you my newsletter? And now, these people who I only talk with once every five or 10 years, hearing from me every month. And it seems like there's really something to be said for that.'cause now if I call, if I call one of these friends I haven't talked with in years, it's not exactly like I'm just. Starting cold with a five year gap. It's at most a one month gap 'cause they've been getting my letter and maybe reading it, but at least seeing it. So they're at least reminded I exist every month
Ryan:Yeah.
Jason:seems like that seems like a really valuable career benefit.
Ryan:Yeah, I think you're right there. What about the podcast? Are you gonna keep podcasting?
Jason:That's one of the last things I would cut, I
Ryan:Yeah.
Jason:Yeah.
Ryan:That's gotta be good for career networking. I.
Jason:Oh
Ryan:More. More so than probably any of the other things you mentioned.
Jason:Yeah. Like for example, at Sin City, Ruby, I went and had lunch with Dave Thomas it's it, that can be traced directly back to the podcast. That's the only reason that happened. And it's in what other scenario would I find myself having lunch with Dave Thomas, or arm wrestling Obie Fernandez
Ryan:Right.
Jason:at the previous Sun City. Ruby. I,
Ryan:That was a epic battle if I recall.
Jason:yeah. Yeah, that was, it was a pretty even match. But yeah, the podcast, a lot of people don't realize, but maybe you guys are starting to experience this with this podcast. One of the biggest benefits from a podcast, from hosting a podcast is the people you get to meet who you have on as guests. You can get access to what you might call like high status people who are like really busy and in demand, and you wouldn't get a chance to have a relationship with any other way. can just you can eventually count them among your friends and maybe you'll end up just you might hang out in person. You might have each other's phone numbers and next thing you know, you just you're friends with all these like famous, important people. And that's a pretty big benefit.
Ryan:Yeah, for sure.
Brendan:Yep. It's been great catching up. I've actually gotta get going to a standup meeting here shortly, so
Ryan:I.
Brendan:prob probably a good time to call it. But is there anything else you wanted to, talk about really quick or any, I guess we could go through where people want to find you on the internet, all that? We've done that before, but we should probably do it again.
Jason:Yeah. Yeah. And if I may plug a couple things. So my snail mail newsletter, it's called Nonsense Monthly. you can subscribe to it by going to code with jason.com. And there's a link in the nav that says Snail mail newsletter or something like that, maybe just says snail mail. Anyway, you can sign up there. It's the current price is 50 bucks a year, so pretty affordable subscription to get the world's greatest snail mail programming newsletter your inbox every month. My, my podcast is called The Code with Jason Podcast. for all the stuff that I do, you can go to code with jason.com as a starting point and find everything else from there.
Ryan:Awesome. Thank you for joining us again. It's always a pleasure.
Jason:Thank you guys.
Brendan:Yeah, thanks. See.
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