Skip to content
500: Celebrating with past hosts episode artwork

May 26, 2026 58 min

500: Celebrating with past hosts

from The Bike Shed Hosted by thoughtbot

The Bike Shed celebrates its 500th episode with hosts new and old as they reflect on the show’s history and ask, what’s new in your world? Our past hosts look back at their time on the show, their favourite moments while hosting, what they took away from producing the Bike Shed, and what they might do today if they were still in the hosting chair. — Your hosts for this special episode of The Bike Shed have been Joël Quenneville, Sally Hall and Aji Slater. Joining them have been our returning hosts Derek Prior, Sage Griffin, Stephanie Viccari, Chris Toomey and Stephanie Minn. Listen back to some of our guest’s highlighted episodes Bike Shed 14: An Acceptable Level of Hassle with David Heinemeier Hanson Bike Shed 172: What I Believe About Software Bike Shed 180: A Citizen of the Internet with John Resig Bike Shed 302: Observability with Charity Majors Bike Shed 325: Pranting Bike Shed 404: Estimation If you would like to support the show, head over to our GitHub page, or check out our website. Got a question or comment about the show? Why not write to our hosts: [email protected] This has been a thoughtbot podcast. Stay up to date by following us on social media - YouTube - LinkedIn - Mastodon - BlueSky © 2026 thoughtbot, inc.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

500: Celebrating with past hosts

0:00 58:21
of matches

Transcript Auto-generated, may contain errors

Hello and welcome to the 500th episode of the Bike Shed, a podcast from your friends at Thoughtbot about developing great software. I'm Adi Slater. And I'm Joel Kinville. And for the last 12 years, the Bike Shed has been here to share a bit of what we've learned along the way. To celebrate this very special moment, episode 500, we've decided to bring back all the previous hosts and ask them what's new in their worlds.

Let's start by rewinding the clock to 2014 when the show first started. Just to put you in context, this is the age of probably just getting rails for, CoffeeScript is still a thing. Two thought-waters have the idea of starting this new show called the Bike Shed. So I'm joined by Sage Griffin, one of the original hosts of the Bike Shed. I am so happy that you could be here.

I am happy to be here. So I think we need to start this off the way that we always do around these parts. What's new in your world? Well, it's been a while. A lot of stuff happened in the past almost a decade.

And with full time doing open source was leading the crates.io team for a number of years. For anybody not familiar, that's the Rust equivalent of RubyGems.org. Then burnt out on open source during the pandemic and kind of retired from that. Distant at the Rust Foundation trying to make open source funding less terrible. And these days I'm not doing much of anything. I'm finting a bit of a sabbatical dealing with my health and hopefully I'm going to be rejoining the workforce sometime soon.

But we'll see how much the current AI hellscape makes that feasible. That's true. It's hard to tell what the horizon of the hellscape is going to look like in the next couple of months. Yeah, if we really are going to go the way of your use of AI ends up being a thing in performance reviews, I'm just going to go open a bakery or something. I don't know. I think a lot of developers and pretty much every developer I've ever met has some kind of analog backup plan or like dream to run into the woods and live in a cabin and knit all day or something like that.

Yeah. Do you have one top of mind that you wish I had an obvious like alternative but software engineering is all I know. Yeah, I don't have a viable obvious alternative but I do dream of opening a Detroit style pizza restaurant. Detroit style seems to be having a bit of a moment now as well. So it might be time. I don't know. Probably not.

About a year ago I had the idea of kind of flirting around. Alpurky, we have this miniature golf course that's been abandoned since like, I want to say 2016 or something like that. And it has like big statues of dinosaurs and giraffes and the property owners kept those statues maintained. It was like a fixture of my childhood and I kind of thought about seeing about me buying that and reopening it but then somebody else beat me to it and now it's reopening later this month. So glad to hear that it's reopening but sad that it got snapped out from under you. Yeah. Oh well.

So just to kind of reminisce or think back on your time on the bike shed, most of which was the formative part of my early development career. If I can be a bit of a fan person about that. Do you have a favorite like memory or episode that you recorded? It should be hard to say a favorite episode because it's been so long. I don't really know that I remember the specific episodes.

I definitely remember though every year for RailsConf we would fly out with a bunch of recording equipment. Derek and I would go and then our editor at the time, Tom would also come with like just massive amounts of equipment and I would run around the conference getting all the various other rails and open source folks to come do an episode and we would do like a live episode with them instead of remotely. And we alternate between like a new one and one from RailsConf for like three to six months and basically whenever we had holiday breaks or whatever, didn't have time to record those episodes were how we kept it weekly for the entire time. And those were always really fun. I remember Aaron Patterson was always a fun guest to have. Really? I can't imagine.

Yeah, no, he seems like such a boring, un-entertaining person. He'd been a live audience once for an episode that we did with him and that was a lot of fun. Yeah, that sounds great. Is there anything that you learned from hosting the show? Career-wise, development-wise or not?

I mean, before the show I was very much like focused on being an IC and the show started kind of right around the same time. I wanted to start giving conference talks because, you know, I joined ThoughtBot and giving, and if you work at ThoughtBot you give conference talks and write Thought Leader blog posts. That's what you do. I say that jokingly, but my wife now works for ThoughtBot and is giving conference talks and writing Thought Leader blog posts. But starting the bike shed really, I think was a big part of kicking off. Like, my realization that I was much more interested in teaching others than just coding.

And even like as I've kind of left open source and looked for more traditional roles, I've always looked for roles where I'm able to spend a lot more of my time mentoring other folks than just writing the code. Because writing the code is great, but helping humans along their journey is much more fulfilling. And, you know, I don't really do much Rails these days, but my wife Tess does. Sometimes I tag along to RubyConf for RailsConf or we went to the last RailsConf. And even now, like folks would, even though I look absolutely nothing like I did back when I was on the Ruby conference circuit, some folks, you know, have followed me along, recognized me and like still came up to me and told me how much they appreciated the early bike shed, which I was blown away that anybody even remembers it.

So was that part of the kind of beginning of the bike shed, your realization that you wanted to contribute back in, look with your experience, that sort of thing? How did the show come about? I mean, the show came about because Chad said that they wanted to start a new podcast and ask for volunteers. And it was originally me and one other person in the Denver office, but then she decided she didn't want to do it, so Derek jumped in. And we had recently been on a project together and sort of did a very interesting experiment with taking Sandy Metz's rules as literally as humanly possible.

And so, you know, decided to talk about that. And, yeah, I don't know, we did the one episode and then we just really liked doing it. So we kept doing it until they took the microphones away and said we couldn't do it anymore. Well, if they hadn't taken the microphones away, if you were hosting the show today, what do you think you would want to be talking about? I don't think I would be hosting the show today. I wouldn't be a good host anymore.

If I were doing it today, I would probably just be complaining about crypto and AI and how much worse AI is making both tech and the world at large. And I don't think very highly of the folks who are really into AI right now. It would be very entertaining. I don't know. I'm glad the show has continued.

One of the things I was building towards the end of my hosting the bike shed was an ORM for rust called Diesel. That shipped 1.0 and I kind of recruited a core team and then have since more or less stepped away from that project. And that's another one where it's like, it's really cool to build something and then see it continue without you. Right. Yeah.

You know, it's like children, but computers. Well, I'm really proud and happy to be a part of the continuing legacy of the show and of the bike shed. And thank you so much for joining me. Of course. Thanks for having me.

And now I'm joined by founding cohost of the podcast, Derek Pryor. Welcome, Derek. Hey, Joel. How you doing? I'm doing great. For many of our listeners today, they will have maybe not heard your voice before,

but you were one of the people that originally created the bike shed. Tell me a little bit. What was the story of that? How did the bike shed come to be? You know, I think the earliest conversations I remember having about it were from a Rails conference Chicago.

Can't exactly remember which year, but there were a group of us sitting around the table and talking about how, you know, the flagship podcast, the giant robots podcast has sort of gone off in a business e-direction and that we missed having technical web programming like podcast out of thought button. So we threw that idea around and somebody said, like, Hey, why don't you do that? And Sage was like, I would be interested in this. And we sort of sat on it for a while, probably like a year until we finally, I think Chad made a post that was like, Hey, we should do this. And then we sort of dug that idea back up. And I was very nervous about doing it. I didn't think I'd make for a good podcast post, but also at the same time, very excited to try it.

So it's exciting to see that it's gone. 500 episodes is quite an accomplishment for any podcast, obviously through a series of posts or whatever. But I would imagine that most podcasts don't make it past three episodes. So congratulations on 500. Yeah, the thing that you've created is taking on a life sort of beyond you has gone through a few generations of posts and is now still going.

Yeah, it's really amazing to see every time I see a pop up in a feed, I get a little smile of like, Oh, I helped. I helped start that. And to see it, like I said, see it all the way at 500 episodes is astounding. What was it like in the sort of early days of the podcast? Did you sort of immediately know what it was going to be about?

Or did you have to spend a few episodes or maybe even, you know, first year or so, maybe finding your voice finding what exactly the podcast wanted to focus on? Yeah, I mean, I think early on it wasn't natural for either Sage or I, we had like a list of topics and we would be like, this week, this is going to be our topic. And we would have it planned out like, you know, we'd have a Trello board of topics that we wanted to talk about. And I think that went okay, except like I often entered every conversation with like a list of things, a list of notes, a list of points that I wanted to hit, right? And I remember early on maybe third or fourth episode there was an episode that I listened back to because it was my job to do the show notes after the recording.

I listened to the recording to the show notes and I was like, we can't release this. This sounds so bad. This is so wooden. So there's like a lost episode of the bike shed somewhere that we ended up re-recording. We did use the topic again, but eventually, I don't know, maybe I want to say like maybe we did some live recordings from Rails Conf one year.

And I think that's sort of where we found our footing actually, which is interesting because it was never really an interview show where we brought people on except for when we went to Rails Conf. But I think it's just sort of doing all of those, we did like, I don't remember, I want to say like five to ten different recordings at the show. So doing all of those recordings gave us a whole bunch of reps at once and it was just, it made us more comfortable. Also Sage and I having time to be in person and connect a little bit, like made it a little bit more like a personal conversation, which I think is how it grew from there. It was just like, we would have ideas about what we want to talk about every week, but we never fully had a whole rundown planned out or anything like that.

I found that having that personal connection between the co-hosts really makes a difference in terms of the output. Yeah, absolutely. I think that helped a lot. Even with the guests, right? Some of the guests were easier to connect with than others for us.

The ones that were well known to us or that we had a history with around a topic or something like that worked really well too. So when I stepped in and replaced Stephicarry and Chris Toomey, they always opened the show by asking each other, what's new in your world? Is that something that you and Sage did or did that come later? I think that probably came later. That's probably a Chris and Steph thing. I think generally one of you been up to.

So maybe the same kind of spirit. I don't know that we had a particular opening other than saying hello to each other and then just having a conversation. I don't know that we had a hook like that. I have to go back and see. It's definitely now become a little bit of like almost like a tagline for the show, which is kind of fun.

So I'm going to ask it to you now, Derek. What's new in your world? Oh boy. I feel like I'm going to give an answer that so many people would give to this, which is, let me back up a little bit. I think there was, I'm going to go back and say, what was old in my world.

I would say sometime between 2022 and 2425 somewhere in there, I sort of like lost what I would call a passion for the job that I was doing. It was just a job and it was fine. I enjoyed parts of it. I didn't enjoy other parts of it. But when the day was over, I didn't come back and sit at my desk because I was really interested in a problem anymore and that felt wrong to me.

But I couldn't quite put my finger on it. I just sort of assumed maybe it's, you know, I'm 45 years old. Now I've been doing this for a long time. Maybe this is just how it gets when you get older. But recently, as recently as like January, throwing myself into coding agents and things like that have really sort of like sparked my creation bit, I guess I would say.

I'm creating a lot more than I have in years past. Whereas before, I'd be like, oh, I could do something that I could build something that does this. I would be like, ah, this is going to take so much time. I don't have like, do I really want to invest that? Do I want to do that for my next three weekends?

And now I can just sit down and like spike out an idea in regular conversational language and get to something really useful. And so the amount of like useful software that I built for myself or for organizations that I work with, like charitable organizations I work with over the last three months has really given me a lot of energy. Like it's been so much fun. And I know that there are like, AI is like a multi-edged sword. It's not even two edges.

But it feels like one of those things that like, you know, there's the overused expression of like you can't put the toothpaste back in the tube. And I feel like that's sort of where we are. So I'm trying to wrestle with like, okay, well, this is here. What's it good at? What's it not good at? What can it do for me? What's it doing to me?

And so all of that has really just kind of got me thinking again. It got me like, I would say like back online, right? Back reading things back back at my computer to do personal projects at night, things like that. So I'd say that's probably the newest thing in my world is sort of coming back to technology as a hobby in the last three to six months. That's a major thing.

Yeah. I find that, you know, people I talk to have a whole range of feelings around AI and the impact on their work. And for a lot of us who software is a hobby, right? There's that maybe that pull some people feel that it sort of takes the fun parts away from the job. And then others like you were saying like, oh, it right brought back the spark and now I've got my hobby back.

I am very empathetic towards folks who feel like, well, I really liked crafting the code line by line because I really enjoyed that too. And so I don't want to say those folks are wrong. Like, I think they're right and I'm right. Like everyone has their own experience of what it's doing to them and where they are in their journey. Exactly. I think that's part of the interesting thing now that I've been doing this for a handful of months or so is sort of the reflection on like, okay, I understand now what it's like.

I understand now what it's doing for me. I understand the problems and now we're able to solve it. I didn't have the time or energy for or in some cases I didn't have the knowledge for. But what is it doing to me? Like, how is it changing? What I produce or how is it changing? How I interact with my coworkers or how I approach a problem or what I consider to be a solvable problem versus a non-solvable problem?

Those are sort of the reflections I'm having more recently. I don't have any great answers for those. But those are the questions I think are really fun. I'm having a good time thinking about that so much so that like I think my wife is tired of talking about AI. I love the self-awareness there. I wish more people would ask the self-reflective questions. I will ask you a self-reflective question and you may not have a good answer for this.

But is there an episode that you remember doing for the bike shed that either is a favorite or maybe one where you felt like it led to a lot of personal growth? That's a really good question. I think it's been so long now. It's been eight years or so. The podcast is sort of one thing in my mind. It's not 160 or so episodes that I did.

You have auto-compacted memory. We had to compress all that context. I think there were different exciting moments about the podcast. I think getting to talk to DHH at the time was kind of a big deal. There was what now seems like pretty tame controversy around the inclusion of action cable I think it was at the time in Rails.

So getting to talk to him and feeling the pressure honestly of like this person's a guest on my podcast and I want to talk to him. But also being like, I have some strong opinions about this and I want to push back on some things. That was an interesting experience. Honestly, some of them are the early episodes. I really enjoyed the episode we did with Sarah Mae from that first RailsConf as well. A lot of the interview ones.

When we did live episodes, particularly at the second or third RailsConf that we went to seeing that people cared enough to show up to a recording or come talk to me and say hello and say they enjoyed the podcast and things like that. That's the kind of stuff that I think left a mark on me or made an impact on me. So literally the friends you made along the way? Yeah, I guess that's really it. Like I said, the podcast is just one thing in my head and really it's about the people I got to talk to, the opportunities that brought to me.

I don't recall the specifics of any one conversation except if I were to pull up the backlog episodes I thought I could remember what each one is. I'll say it's a talent of any time there's a Save My The Bell episode on TV within the first 30 seconds I can tell you exactly what the whole plot of the episode is. I'm like, oh yeah, this is the one where blah blah blah blah blah. I'd imagine the same way about the first hour and many episodes of the bike show that I was on. But in my head right now, they're just one thing.

It's been great to have you on the show. Before you leave, I want to ask you a selfish question. If you were a host today on the show, what is the topic that you would want to talk about? I mean, I think I spoiled it in my earlier answer. And that is sort of reflections on what we're getting out of AI and what it's doing to us.

I think you could do an entire season of the podcast just on that question alone. Obviously, I think there's a whole bunch of people who probably listen to this podcast and are like, oh, another person wants to talk about AI. So you can also go the other direction and be like, now we're going to do an entire season that doesn't talk about AI at all. And I think that that would be really well received as well. But that's sort of the first thing I just remind because it's the thing that's in my head.

Like what is it doing to the way I work? I work at GitHub where we're on the receiving end of a lot of the output of AI and just seeing exactly what that has done, the scale that that is bringing. I pulled up number of the other day that showed we have 76% more PRs created in February, 2026 than in February of 2025. Wow. So just the scale of creation that we're wrestling with and the scale that we're wrestling with makes for really interesting problems.

So I think there's technical and societal questions to wrestle with there. It's really just a matter of whether the world needs more people talking about that right now. And I think I guess the world needs inform people talking about it right now, right? A lot of the opinions I hear on AI come from folks who have dabbled or have not really engrossed themselves or they come from people who are on the other end where it's like, all I ever do is talk to an LLM all day every day now. And so I think coming from folks, I think thought about it is pretty well positioned as somebody that works across different companies and different environments and different technology stacks and things like that to say, this is what we're seeing across several different teams, across several different companies.

And so I think bringing that sort of practical perspective is good. Well, thank you so much for coming on the show for the anniversary episode. Congratulations for building a thing that went to 500 episodes. That's an accomplishment. Congratulations to you and thank you to ThoughtBot for keeping it going.

And now jumping forward to a new era. Welcome back, Steph, to the bike shed. Thank you. It's good to have you here. It's so cozy to be here. It feels like home.

Nice. I'm glad to hear that. Well, I'm sure you'll be familiar with this. Let's start with what's new in your world. Yes.

It is a very familiar question. The thing that is new for me is that I am taking a break from work and I don't have an end date on my break. Oh, how does that feel? It's a mix. It feels really good.

I mean, on one hand, spoiler, you know, not working is awesome. On the other hand, there are a lot of things that I do miss about work, but I'll share a bit more of the details. So when Chris and I ended our season as co-host on the bike shed, I had my son and kept working at ThoughtBot. And then over time, I made a switch and went to Moraki. And I loved working there and had a great time with my team.

But after a while, I decided it was time to take a break and taking a break is putting it mildly because I was in such a constant state of burnout, which I think most parents go through. And I thought that burnout had a floor. It turns out I had a shovel and there was no floor. I just kept taking it. So after a while, I realized that it was time like my health was getting to a place that I was very worried about it.

And so about August 2025, we decided it was a good time for me to step away from work and prioritize my health. And it's going really well. So my days are focused on a three-year-old and my new KPIs are scooter velocity and consumed veggies. Those are my new metrics. That is beautiful.

I'm really happy for you. I took a short break in 2020 and it was like world-changing. I love that you get to do this. How long was your break? Mine was just three months.

It was, I don't know if you remember, 2020. It was a little bit of a hard time for everybody. And so I took like, I think it was August, September, and October or something like that, three months, and literally just kind of sat around and read books and worked on knitting things. And it was so such a good brain reset. I was worried that I would forget how to code.

But I think when I came back, I actually, I felt like I was doing a better job than I had been doing before because I think it just really needed to be set. Yeah, absolutely. I'm so glad you did that. And yeah, I did forget. I had that same concern.

I'm like, oh, I'm going to forget how to code. And I came back and I didn't necessarily forget how to code, but I did forget how to them. That's the one that my brain needs. We're going to let this one go. So I had to relearn the film when I came back to work.

So then it's not like running back. It wasn't for me. I mean, it came back eventually, but it took some, I had some crashes and then had to get back on the bike. Yeah, that's fair. So looking back on your time, I remember really enjoying the era of Chris and Steph hosting.

What was your favorite episode that you recorded? One that always stuck with me that I really enjoyed. It's one that Chris recorded with a guest and it's one with charity majors. I think it's observability with charity majors and I always loved that episode. It just felt so flawless and how well they carried a conversation back and forth because as you know, sometimes when you have guests, it depends on how well that flows.

That was always one of just my favorite episodes to listen to. The one for Chris and I, one of the ones that we recorded, anything with a funny intro was always loved. But there was one in particular where we were taking listener questions and I'm pretty sure that's true. But we were talking about what is the opposite of ranting and we couldn't think of the positive version of ranting and Chris loves poor mantos and switching words together. And so he came up with prancing and I can't see it now.

So for the rest of my life, anytime I need the positive version of ranting, it's always prancing. And I think that's the name of the episode is pranting. But I also imagine the listeners like were probably dying listening to us because they knew the word that we couldn't think of and we often don't Google things when we're talking on the podcast. So we weren't looking it up. So yeah, check out, check out observability with charity majors and pranting for anyone who hasn't listened to those episodes.

That's beautiful. Prancing, is that like praise ranting? Is that what that portmante was? Exactly. Yeah, praise and ranting just switched together.

And I'm going to take a guess here. Was the words we're trying to land on raving? Yes. Yeah, okay. You're right there.

Yeah, we could put the word rave for some reason. And there's others too. But rave was the one we were trying to get to that our brains could not land on. Yeah. I feel like when you turn the microphone sometimes like part of my brain just disappears.

Yep. Apparently. What's something you learned from hosting the show? I learned a lot about showing up and doing a hard thing because podcasting is hard. There's a lot that goes into it.

I also learned that once you start recording, that is when the universe will make noise. So that is when your talk will start barking. I think you mentioned when you're talking just while recording that you have a bird that will knock on your window. So the universe must make noise as soon as your audio goes on. I also learned that I really like listener questions.

That was one of my favorite. Like I love that we brought our own content and experience to the podcast, but taking listener questions was one of my favorite. Yeah, we haven't done a listener question episode yet since I joined, but I think we're planning one soon. So send us your questions. Send them in.

How did the blanks had changed your life? I mean, the big one is I became really good friends with Chris. I mean, that's the best gift that came out of the bike shed. That was just wonderful. And the other thing that changed my life is the lens that having a creative outlet like a podcast gave me.

So knowing that I was going to show up each week and share something with the world, then each day, all of like the events or mundane things, I had a more of a narrative lens to look at them through. So something went wrong than I could think about. Oh, what was this interesting? Is it something I can share? Is it relatable or something great?

Then I got to celebrate it on a podcast with Chris. I really enjoyed that narrative lens. And I think it's wonderful to have some type of creative outlet in your life that then helps you carry that lens. So that's probably what changed for me the most is having the friendship with Chris, but then also developing this new way of just looking at everyday events and then how you would share someone. Yeah, absolutely.

I've learned that. So I feel like, you know, if I'm having a really terrible day, sometimes it's like, well, if nothing else good comes out of this, it's going to be something worth talking about on the podcast. Exactly. If anything, it's good to you and drama for the show. Yes.

If you were hosting again today, what's something that you would want to talk about on the podcast? I think I think I have to. The first one would be, so when I was going through that deep state of burnout and before I was at that point, then I was able to take a break from work, I have a lot more understanding for what it's like to work with like an unpredictable schedule, having child in my case, and then also what felt like chronic illness to me because every time my child was getting sick, I was getting sick twice as hard because my immune system was just so, so low. So I think an interesting topic that selfishly I'd love to hear is how do we make work manageable for those with either a recurring health concern or maybe a schedule that's unpredictable.

And it would be great if it came from multiple perspectives, if it comes from the worker in terms of like, what do you do to de-risk your work, knowing like, hey, I may not be online tomorrow. So what can I do today in case I can't be here tomorrow? And then also from a manager's perspective of like, how do we help then everyone on our team also de-risk and have a environment that if they are here tomorrow, that's okay. And we can still carry on. And I think there's a lot of overlap with software and how we can manage our schedule and manage our systems and our communication. That would be really interesting.

At least I would find it really interesting. Yeah, I find that interesting too. And I'm digging. We may be asking you back to talk to us about that because I would love to talk about that and hear about it. Oh, yes, please.

I will share all the details from what at least what I tried, what worked and what didn't work. That'd be great to talk about. The other one, this is a little different. So this isn't necessarily this is a different idea from from Bike Shed. But for podcast in general, working at larger companies, there's often a difficulty in having a lot of collaboration in community when you have such a large team.

Like even at ThoughtPods, big enough that there are people that you may never gotten the chance to work with. And many, many moons ago, a former ThoughtPods, Edward Lovell, he started a podcast that was just internal and was getting to know other ThoughtPods. And I really enjoyed that. And I would take it one step further and have it getting to know people on your team, but also getting to know their work and what they do and something that they would share interesting because especially larger companies, it's very easy that you may not have any idea what another team does. But you might find it really interesting or be able to collaborate with them. So I love, love the idea of internal company podcasts.

Yeah, I think that if I were going to start a podcast, that would be my podcast. I just need a company to be like, Hey, come start a podcast. Stephanie Corroda has been doing something similar to that recently where she's been going through shoutouts that people have given to their own on Slack. Okay. And finding patterns and then interviewing people about things that they're frequently recognized for, which has been awesome.

You know, that's amazing. And that doesn't surprise me one bit. Stephanie Corroda is brilliant. And that sounds fantastic. Yeah, it's really cool. So a little bit of that. What are some other podcasts you listen to? Although, I don't know what the kid, maybe you have no time or they're all about kids.

You know, you're right. I don't listen to podcasts. I haven't much. Or if I do, I really tune into the podcast that are more comedy driven. I still listen to the mic shed because it's a cozie home from me. I love hearing what's going on with the show. I love the co-host setup that y'all have gone right now.

How it rotates between you, Ajini and Joel. And that's so much fun. I get a lot of joy from that. Between the mic shed, it would also be good hang with Amy Fuller. I like that one. Oh, I love her. Yeah. She makes me laugh. It's often very positive. It goes into weird places you never expect with a host.

And so those are the types of podcasts that I like. I also really just enjoy like cool people talking to each other and having a good time. Yeah, having a good time. And the parenting ones, I found a good parenting one. Have you ever listened to a good parenting podcast?

I used to listen to this podcast. I'm not sure if they're making it anymore. I still listen to it partly because my kids are going off to college. My parenting life is different. But it was called One Bad Mother. It was a really great podcast for the realities of what being a parent is actually like.

They had a segment every week called Genius and Fail where the hosts would share a genius thing they did that week or heard about for parenting. You know, stupid things like, I have snacks in the car when I pick my kids up from preschool. This is a little tiny hack that has made my lip better. Or fails. Like your kid helping themselves to a snack from the floor that is chicken nuggets from two months ago.

It just makes everything really relatable. You know, like, hey, yeah, I've done that fail too. Or, oh, that genius would be helpful. So that's the one parenting podcast that I ever really connected with. That's the Parenting Energy I'm looking for. I will check it out. Thank you.

Yeah, their mantra was, you're doing a great job. That's just all you need on repeat. Yeah, you're doing a great job, Steph. That's a little dopamine hit every day. Hey, you're doing a great job. You are.

You are. Well, it has been great to talk to you. And yeah, I think we should bring you back for another episode. Well, thank you for this. This was a lot of fun. So thanks for letting me have a little part of my channel.

Hello, back again. I am joined by another of the illustrious former hosts of the bike shed, Chris to me. How are you? What is new in your world, sir? Hello. Thanks for having me. It's probably gonna be back here.

What's new in my world? I appreciate that question. Steph used to ask me, how are you? And then just leave it at that. And for some reason, that question would always confuse me.

And I did not have to answer. Do you give the real answer or do you give the radio answer? So we switched it to what's new in your world, which we give a much easier question to answer. Probably most relevant thing is I had a kid about 15 months ago, a little over 15 months ago, which that will really change your world a whole bunch. So that has shaped a lot of what's been going on in my world. But otherwise, you know, I joined a startup that startup did the whole grow and then crash into the other thing.

Now, I'm at a different startup, which I've been at for about three years, coming up with August Health, which I really enjoy doing great work. I think we have one of the largest expat Thapaw groups out there. And GitHub has the most ex Thapawters. We have the second most with something like five or six, maybe seven of us here. Okay. So it's a very familiar development team, sort of practices and whatnot. A lot of the Thapaw ethos is in the next day today.

Yeah, that's what I'm up to. That sounds great. That's great. Yeah. I've always heard of the Thapaw to GitHub kind of pipeline and had assumed that that would be my career trajectory. But yeah, still here, still loving the Thapaw.

So I'm not really thinking about that just yet. I mean, it's a great place to hang out. I give it a good seven years, which is a lifetime in tech. I've got to see lots of different places and host a couple of podcasts and do a bunch of things. So I highly recommend an extended state of Thapaw.

Yeah, I am familiar with several of your different sort of publicly facing projects at Thapaw from my pre Thapaw days up case, helping me through one of my first dev jobs and of course, as a long time, bike shed listener. I enjoyed listening to your time there as well. And I even remember there was a RailsConf, where you did a few live recordings and I attended one of those as the only person in the room listening to you talk to Eileen Do you have a favorite episode or do you have some that have fond memories for you as you think back to your time?

Yeah, there's certainly a handful that sent other, a couple of external interviews that I got to do that were really meaningful for me. I got to talk to John Reza, creator of jQuery, which was so formative in my development journey from way back in the long long ago, but it was an interesting conversation to have and someone who had built something so meaningful to me. Likewise, Gary Bernhardt was another really meaningful one. He's someone who just so deeply informed the works that I did, like getting to actually chat with him and discuss that. And in both cases, just really, you know, say thank you to these people who had given me so much was really meaningful, but you kindly sent over this list of questions beforehand and when you asked this one, there was a very clear answer, which was Bike Shed 172, which is what I believe about software is the name of that particular episode.

This is the first time that I had Steph on as a guest. So Steph then went on to become my co-host for a number of years. I've got how long we hung up together in this podcast. But at the time, I'd taken over the hosting range, had done a little bit of a tour of both folks outside of the up and inside of the up and I was in the back of my mind. I was looking for a co-host. I felt like that was the right format to the show. Everybody kind of thought behind the scenes.

Who feels like the right person that I have a rapport with, that we can have some meaningful conversations. And that day, Steph came on and that episode just sort of encapsulated, and it's right there in the name what I believe about software. And I think for both of us, we had just such a natural conversation that I've listened back to it a couple of times now, actually, just because it sort of reminds me of so much of, I think, what's up on is about how there's the tech part of things, but then there's the human part of this work that we do. And then it started a wonderful journey where Steph and I got to hang out and chat on a podcast once a week for some number of years. That's really great. And to have that as an artifact to kind of go back and revisit and kind of revitalize your core beliefs about what you do, that's a really excellent thing to be able to tap back into.

Are there any things that you feel like you learn from doing the show, that you brought into your work outside of or even outside of career things? I think the main thing that I took away from hosting was this is more personal to me, but I'm very much a verbal processor. Turns out I figure out what I'm thinking by saying it out loud. Very Michael Scott, like I'll start a sentence and not know where it's going to end up. And then I get to the end and I'm like, I kind of agree with that.

But it is for me a really meaningful way to process and work through things. So the bike shed was a really wonderful sort of forcing function place to explore ideas, things like that. And now sort of in my day to day work, I try to keep that around and I'm all the more ready to have a conversation with someone, reach out to someone and say like, hey, I'm struggling a bit with this thing. Can we just talk it out and recognizing that sort of core thinking mode for myself? The bike shed really highlighted that to me. So that's probably the main thing that I learned.

Are there any thoughts that you sort of arrived at that surprised you when you got to the end of the sentence? No, I think I tend to agree with what I think I just don't know it until I say it out loud in a lot of cases, which as I say, it is a scary prospect. But here we are. I would often listen back to the show and I would do some amount of prep, but not a ton of topics that I wanted to talk about, but not the details of the topics. Like, oh yeah, this was a thing that I did this week. Seth and I can talk about that. And then I would have a conversation about it and I would listen back sometimes in editing or other show notes.

And I'd be like, oh yeah, okay. Now that I hear myself say that that that is what I think, which was always a surprise, but a surprise at that's how my brain seems to work. But not so much though that I was like, oh, I didn't know that I thought that. More like a crystallization of the things that I was thinking. And similarly, like chatting with Steph, getting that back and forth and considering such a thoughtfulness to her work that was always an incredibly useful space to talk about explore ideas and cases work with her and things that she was thinking through.

And so it was a lot of fun. Are there things that you're working through, thinking through in the last couple of years that if you had been hosting the show through you think you would have talked about or what would you be thinking talking about? There's this thing called AI. I don't know. I think it's AI, right? Is that how you say it?

I think I'm pretty sure I'd have to go check my notes. Okay. Yeah. Yeah. I mean, what a wild time in the world of software. And it's actually it's an interesting one where I wonder what it would feel like to be in the hosting seat or be in a position where I need to talk about this thing.

Probably need to talk about this thing. I don't maybe week more at each week, but would have to address this elephant since this nine thousand pound elephant in the room. And yet it's such a, I would say still in a sense, still very much being formed. What is the actual long term impact going to be on the day to day work and the industry is old. I'm like, what a wild time. So I would probably be talking about that. But I would also, I think really try to make sure that's not the only thing I'm talking about because I know there are plenty of folks who are going to talk about this thing.

I'm not super interested to deeply disinterested in it as a topic. And I imagine that's a difficult thing that you're navigating these days. So from hosting perspective and also maybe from a life and work perspective. Oh, 100%. I think we all are really and whatever aspect of this work that you're going to do, whether it's talking about it publicly or just sitting down to accomplish something at your desk.

It's going to be part of how you're approaching things. So 100% it's been on the show and will not be going away anytime soon. So yes, I will say for me, the one like the clear positive is that as I was talking about, I'm sort of a verbal processor, et cetera. Having a sort of a thinking partner has been really useful for me. And I do a lot of dictation now as a means to explore the work that I'm doing.

And that has been exceedingly useful often have like a piece of work. I'm like, how do I even start this? And so I'll just kind of ramble about the problem. And then there's this magical tool that will give me surprisingly meaningful feedback and direction and sometimes just the answer to the question that I asked. That's weird. I'm sorry. It's very weird. But also magical. And I try to at times focus on the positives of it.

I think that's probably the thing I'm going to talk about. Yeah. Well, I want to pass it on to one of the other former hosts who is going to be joining us here in this episode. But thank you so much for joining me and giving us all a little update about what you've been up to and what the episodes that may have been in the interview meeting years would have been about. Well, thank you. It's such a pleasure to hop back on here. Say hi to folks. Hope everybody's doing great. Both thought about and in a broader world.

And thanks for having me. And now I've got former bike shed co-host Stephanie Minn joining me. Hi Joel. Welcome back. Thank you. It's good to be back. I had to dig out my mic from the drawer that it's retired to.

And I was just showing you on video that listeners can't see, but I couldn't find a little tripod that goes with it. So I have my mic sitting in like a little beverage cooze. You feel like you still have some of your podcaster instincts that are coming back to you? Well, I did have to figure out how to unmute. If you find a switch to unmute the microphone. So I'm going to say no.

But I don't know. I think I'm talking now. So that must be something. So I'll ask you the question that we've asked every other host on the show. You've had your past you a lot of times before. What's new in your world?

Wow. A lot of things are new in my world since I was lost on the show. But I think the main one is that these days I'm working at a little local candle company, a small business here where I live in the Hudson Valley. And yeah, these days I am still doing some kind of computer work. I'm actually in a bit of an operations role, but it's been really fun kind of learning about how a physical product is made.

And I come home every day smelling very good. Oh, I'm sure. Do you have a favorite candle something you make? Yes. So the company's name is called Keep Candles. And recently we were in the spotlight a little bit because our kind of best selling candle is called Wood Cabin.

It's been showing up in a lot of like the bathrooms of a lot of cool restaurants in New York City that they're burning our candles. Some of some really cool dining spots in the city. And yeah, we even made it on the Colbert show for that one. So that was pretty cool. Yeah. So that's kind of the one and only that is a real fan favorite.

Do you feel like there's any perspectives or aspects of your sort of more software engineering job that you've taken to this operations role? In many ways that you see things differently from your colleagues because of your past experience. Oh, yeah. I actually am still coding, like not an insignificant amount. And it's interesting. I've had a lot of thoughts about software development since kind of now doing something completely different.

Like for some reason, I just am making all these connections. I think the two things that I would say are because we live in a digital world, there's just like always opportunity to be automating things and stream mining things and making things just easier. I think we not used to talk a lot about having admin dashboards be really useful and taking care of other internal stakeholders with our software. And now that I'm that person, I get to do it for myself, which is pretty nice. I don't really have to wait for someone else to do it for me.

Then kind of the adjacent thing I've been thinking about a lot to that is helping teach other people the building blocks for how to do little automations, even if it's like how to use a fancier filter to help their mental load when they're having to pack an order to know that the things are filtered to just kind of a certain subset of all the products we have available. Yeah, I have really enjoyed helping people look at things that way. Like I said, because even though it's there's that perfect balance, at least for me, between getting to do something in the physical world while still while still also interfacing with digital systems.

I imagine part of what's really nice with what you're doing is seeing the immediate impact of the changes you're making. Yeah, definitely. It's funny because I actually feel like I've been the most loosey-goosey with my code too because I'm the user of it. And so I don't really, you know, it's like I am only accountable to myself if I just kind of mess around with something and it doesn't work that it's just not anything. But yeah, the feedback loop is so much shorter.

And in some ways has given me actually an appreciation for just doing a thing and just writing some really quick script to do something, whether or not it's like the best code ever. I mean, it's definitely not. But I think I used to feel really, I don't know, for some reason there was just more of a barrier to feel like I could just do those kinds of things, even if they would be useful. But now I find that it is kind of easier to reach in my toolbox. So you were a co-host on the show for several years.

I wonder, looking back, are there any particular episodes that are very memorable to you or that you're like, have a fondness to going back? Like, oh, yeah, that episode was an important one for me. Oh, that's a good question. Well, one thing that I can think of right now is that episode 404 was one that we had done together and I still kind of regret not making that more of a prank episode. Otherwise, I really enjoyed the one where we would talk about our favorite blog posts.

I don't think of the episodes off the top of my head, but kind of things we learned about software over the year that really stuck with us. It was kind of recap episodes. Yeah, yeah, those always were fun for me. And I think because they ended up being things that you and I were particularly interested in or topics that we ended up often revolving around even in other episodes, it was nice to have a space to talk about that. I love those as well.

And we've actually sort of evolved them in that now that we're more season based, every sort of 12 week season caps off with a little recap episode where we talk about things we've learned, things we've learned, things we experimented with. And we sort of taken that tradition and brought it forward to an era of the show. Nice. That's awesome. And I think that's like a nice cadence to be doing that as well.

Do you feel like you learned any lessons over the course of being a co-host on the show? Yeah, I was actually thinking kind of recently. I was like, oh, yeah, I can't believe I did that. Because I remember it being like hard for me. It was just something really outside my comfort zone.

And there were definitely moments that I continue to find it hard. We've talked a little bit about just like that, having to record a week is a bit demanding when you are already having a regular job. And other times there were episodes that I felt really great about because you and I just had a conversation. And I was excited to kind of put some of those thoughts out there and then also to see what was connecting with people, what, you know, what things were relatable and what kind of software challenges other people were facing that were the same was really rewarding. So I think the main thing I'm taking away is that like, oh, I can't do this.

It was something that I did, you know, and I can feel really proud about that. Definitely. I mean, I have great memories of the episodes that we recorded together. Some great content from the Stephanie era of the bike shed. So definitely something to be proud of.

I was just thinking that 500 is such a big number. And it's very cool to be a part of like the history of it. Like I did not have to record 500 podcast episodes because I definitely probably would have burnt out before then. However, because it's like something that lives on beyond any individual host. I think it's really cool that we get to like collectively keep it going that way and like maybe we'll get to 1000.

I don't even know a podcast that has 1000 episodes. There's that beauty right at the passing the torch from one cohost to another. That's really fun with this episode because I'm getting a chance to sort of talk to all the different eras of the show and bring the back. Yeah, especially as software has changed over the years. I think it's really quite cool to be able to document that a little bit with the podcast.

Looking forward to the future of the show. I'm going to ask you a little bit of a selfish question. If you were recording episode 5.01 or something later than that, what are some topics that you would like to see addressed on the show? You know, asking for a friend. Oh, okay.

Well, this is kind of related to some of the things I was talking about earlier because now that I work with people who aren't developers. More and more I've been thinking about how to make building software accessible. And obviously there's a lot of things happening with LMS, right, that you can build an app kind of in no time. But the thing that I think is actually really cool is that at my company, we use a tool called CODA that's kind of like Notion, kind of like this hybrid between Google Docs and spreadsheets. That is in my opinion, I think the right abstraction for people who aren't developers into building custom software because it's kind of the way that Excel really changed how businesses were able to utilize these kinds of tools.

It just has enough building blocks in terms of tables while also being able to add interactivity, like recurring automations or buttons. And I've really, really enjoyed helping people learn how to utilize it to the best of their ability to make their own little, essentially web apps to track our candle tests, things that someone would never build custom software to do. But it's important for our business domain and how we run our business. And so, yeah, that's kind of something that's been on my mind a lot. It's just how cool it would be for people to kind of feel more empowered to know just enough coding.

That's a great topic idea. I guess for our listeners out there, maybe keep your ears peeled for something along these lines in a future episode. Stephanie, thank you so much for joining today. It's great to celebrate 500. Thank you for the years that you were co-hosting, like all that you poured into the show to make it what it is today.

Yeah, thank you for having me back again and congrats to you for 500 as well. That was so cool. Hearing from all of the past co-hosts of the bike shed, I just want to say thanks to all of them for their contributions in making the show what has become and their little bit of history that they were able to share. 100%. And really thank them for being a part of the developer that I've become, really from all of my time listening to the show and participating with it across the ages.

It's kind of cool to be able to see as well, right? Like everybody put their little bit and likely that is what will happen with you and I, right? We will be a part of that history and will pass the torch to someone else. Yeah, episode 1000 when it's completely just recorded by an AI and no, that's not true. That's not what we're about.

So I'm looking forward to it, not only participating in the next era of the bike shed, but also seeing what is going to come after we hand the torch off to the next generation of hosts, whoever that may be. And all of our listeners, whether you've just started listening, this may be your first episode, or whether you've been with us, 500 episodes from the beginning. Thank you for tuning in every week. It's great to have you as part of our community. And cheers to the next 500.

Thanks everybody.

Frequently asked questions

How long is this episode of The Bike Shed?

This episode is 58 minutes long.

When was this The Bike Shed episode published?

This episode was published on May 26, 2026.

Is there a transcript available for this episode?

Yes, a full transcript is available for this episode. You can read the complete transcript on the episode page.

Can I download this The Bike Shed episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.