Skip to content
471: New Hosts Join the Show episode artwork

Aug 26, 2025 42 min

471: New Hosts Join the Show

from The Bike Shed Hosted by thoughtbot

Joël is joined by some familiar faces in today’s episode of the Bike Shed to help reveal some exciting changes to the show as he asks his new co-hosts, what’s new in your world? — Thanks to our sponsors for this episode Judoscale - Autoscale the Right Way (check the link for your free gift!), and Scout Monitoring. Joining Joël Quenneville as your new co-hosts are Aji Slater and Sally Hall. Get to know your hosts a little better by checking out Sally’s recent episode on timezones or Aji’s RailsConf Keynote and handy list of previous keynotes. 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 © 2025 thoughtbot, inc.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

471: New Hosts Join the Show

0:00 42:12
of matches

Transcript Auto-generated, may contain errors

Autoscaling is a simple concept. Automatically add resources when needed, and automatically shut them down to avoid paying for excess capacity. How hard could that be? If you've set up Autoscaling yourself, you know it's not that easy, especially using the native Autoscalers on platforms like AWS and Heroku. That's why you need JudoScale.

JudoScale is Autoscaling as a service, and they make Autoscaling simple and easy, as it should be. You can use JudoScale on AWS, Heroku, Render, Fly.io, and more. It's free for low traffic apps, and unlimited plans start at $25 per month. Autoscale on easy mode at Judoscale.com. Hello, and welcome to another episode of The Bike Shed, a weekly podcast from your friends at ThoughtBot about developing great software.

I'm Joel Kimville, and today I'm joined by, well, actually, a lot of change and a few surprises. I'm really excited to share some new things with you all, and the first of which is I'm bringing on a new co-host, Sally Hall. Welcome, Sally. Hi, thank you. I'm excited to be here.

For those who've been listening to the show for the last few months, you may remember Sally from her episode on paper data structures. Yeah, I really enjoyed that conversation. I feel like we could have talked for several more hours about it. Definitely. It's one of those things where it starts off as the nearest thing it could be to a water cooler conversation in our remote world, some random thread and slack.

And you know what? We need to have this conversation on here because this is just so much fun. I'm so glad we did because we got to dive into more of some of the library science side of things and really saw how organizing information for retrieval versus insertion are not necessarily digital problems or things that have existed for a long time. Yeah, I think as we improve technology, we rarely introduce new problems or get entirely rid of them. Like a 3D printer doesn't jam less than a 2D printer.

It just jams in three dimensions. Oh, that's horrifying. Sorry. Sally, why don't you introduce yourself a little bit to the audience of our show? Tell us a little bit about what your role is, the kind of projects you worked on, the things that you get excited about and tech.

So I'm Sally. I live in Durham, North Carolina. So it is pretty warm here right now. I am a senior developer at ThoughtBot. I do a lot of Ruby on Rails and tend to lean more towards the back end and front end.

I would much rather write sequels and CSS. I've always respected front end work. Now I'm starting to understand it quite a bit better and enjoy it a little bit more even. I tend to work mostly on Greenfield projects, which I really enjoy sort of the... I feel like it's all the fun things about startup without necessarily the job and security that I have always experienced there.

I'm excited for that perspective that you're going to bring to the show because I tend to work more on established projects, larger projects with existing teams, maybe sort of years or a decade plus of history, a lot of tech debt, maybe some more performance-style problems or even just challenges of making major changes in an app that's already big and complicated. So I think bringing someone in on the show who's sort of doing the opposite end of the spectrum is going to be really refreshing. Yeah, I build that technical debt for you. But it is interesting because often we'll start a project and we're the first developers. There's no other developers even in the company yet.

And it's really fun to, in a course of like six months or so, to go from we have no software to we've got an MVP and are starting to hire some people and building our own team for the client. So I really enjoy sort of that rapid change. So you don't get the satisfaction of finding bad code and doing a Git blame on it and figuring out, oh, it's this person. It's either not there or you're doing it on yourself. But yeah, usually when I'm like, what is this and do a Git blame on one of these projects, it's like, oh, I did that.

Why did I do that? But I am currently working on the type of project you do more often. So an established product and we're making some big changes to it with the team. So that has been a different experience. We're really interesting.

I'm curious for you. Is there maybe a type of project or maybe even a type of feature that if you get assigned to it or you self-assign yourself to it, it makes you really happy? Yeah. And this is weird. But I have really enjoyed working on appointment scheduling for medical apps because it was a really hard problem for a while for me.

And then the last time I tried to approach it, some things sort of clicked and found ways to leverage the built-in capabilities of Postgres to do a lot of things for me that I was trying to do in Ruby and actually working on extracting that into a gem now. So I would be really excited to get to do that again and use that gem and see how I can apply it to another project. And listeners who have been following the show for a while may also remember Sally, you did another episode where we talked about time zones, particularly in the context of scheduling systems. So I know time zones are sort of the little bit of the bugbear of a lot of programmers and it sounds like you really actually enjoy them. I enjoy solving that problem.

I wouldn't say I enjoy time zones. And I certainly don't enjoy daylight saving time, but I do enjoy finding sustainable ways to handle those problems and not just sort of putting band-aids on various parts of the app or pretending like we're only in one time zone. Right. The like, this is the thing that's annoying to deal with and I'm going to find a good solution to it rather than, oh, I have to learn to live with it. Yeah.

I'm going to make it, and usually that good solution is I'm going to make it so we don't have to deal with it as often. So it's all about good abstractions. Yeah. Yeah. I guess that goes back to your gem then.

Yeah, totally. Hopefully this solution I've come up with will be usable again and again by other people. And I've named it Michelle after the completely unhelpful scheduling assistant at the bed and breakfast in Gilmore Girls. So it's hoping to be more useful than Michelle. I feel like RubyGems always have these like quirky names and some like lore behind them.

It's like a reference to something that you may or may not get, but it's cute. And it just adds a lot of whimsy to the Ruby world. Yeah. Getting to name things in a fun way. I feel like it's a bit of relief from trying to name things in code, which is rarely fun and often difficult.

So I also like to do that with test data. I will often choose a sitcom and just use the whole cast of characters from that for various test data. So I'm excited to have that on the topic of fun, bringing in a new co-host is not the only fun thing that I'm excited to announce today because we're also bringing on another new co-host. Welcome. I'll talk to you later to the show.

Hello, cats and kittens. Again, for those of you who have been listening to the show for a little while, I'll talk to you a few times, most recently talking about your, I guess, upcoming keynote for RailsCon. That's right. That's right. I got to do that keynote and I think it went over very well.

And I really enjoyed the communication and the time spent with the community afterwards, because it was kind of a historical look back over RailsCon. And I got a lot of stories that day. It's very fun. It was really fun for me having done the episode with you ahead of time and hearing a lot of what your goals and purpose were with the keynote and then seeing you just do all those things that you were saying you were hoping to do with your keynote. And I think you hit all the beats that you mentioned that make a keynote really impactful in your episode.

And then on stage, you just knocked it out of the park and I was there in the audience. For those of you who listened to the show who were not at RailsCon, there was a standing ovation at the end on these keynote. It was really fantastic. We'll link to it in the show notes. The video is already out.

So if you're feeling like, oh, I really want to catch up on that, you can go find that video in the show notes on this episode. Thanks, Joel. So, Ajhi, I'm excited to have you join as a co-host. Can you introduce yourself a little bit for our audience? Tell them what kind of work you do as a developer?

What is your role here at the bot? What are the types of projects that get you excited? Yeah, so my name is Ajhi. It's a short, simple name, but a lot of people have trouble with it. So I'll help you out.

It's AJI and you say it like, ah, gee. That's my little intro that's left over from when I was a thought billion and I've kept that around because it's a nice easy left to start with. But yeah, my role, my title here at the bot is development team lead for the moment. I might as well talk about this now because I'm sure you're going to hear about it for the next couple of months. I am moving staying with the bot bot, but going to a different team because I'm going to be moving to Scotland.

There, I will be a senior developer again, not transferring as a team lead to this new team. So you're moving from the United States? Yes, yes, that is maybe an important detail. I currently live in Chicago, but not for very much longer. The kind of work that I like to do, I think I am generally more excited by Greenfield applications, things that are not only trying to get out to market very quickly, but also kind of find out what are the most important parts of the application through getting to those initial users, iterating on what is the most important value to provide to them right off of the bat, what truly doesn't MVP mean, those sort of questions, and then finding out the way to not only implement that, but also hopefully in a way that is going to be easily maintained and changed as the product develops.

Because a lot of that groundwork that you're laying is either going to go away really quickly or it's going to exist for a very long time, and it won't be years until people will be able to come back and change anything. So you want to make sure that you're setting it up maintainably and again, it's all about good abstractions, useful for many years to come. It almost sounds like a cross between sort of stereotypically what we think of as product manager and architect. I've got a lot of different feelings about the title of architect as it comes into software development that maybe we'll be able to talk to at some point in the future, but I think of it really as kind of laying the foundation and putting the kind of bones of a building in place and then everything that makes the building really run and unique are either layered on top of that, put inside of it and that kind of thing.

So I think the initial building of a structure is kind of a good metaphor until it's not. I'm curious because I do love a good hot take. Thirty seconds. What is your thoughts on architects as a title in software? Thirty seconds.

Yeah, I think it's the wrong metaphor. I think it's the wrong concept. And I think it goes hand in hand with the way that people conceptualize what an engineer is, which is maybe different from what engineering actually is. And there is a lot of baggage that comes along with those concepts because one part of the metaphor works really well. So let's bring the entire metaphor over and it actually really hinders you in a lot of other ways because you've got a particular mindset about how something must be done and in software, the construction and the way the projects get done in the physical world is not the way to do it in ones and zeros.

Sally, I'm curious. What are your thoughts on architects as a role in software? I mean, I think the role, I don't have strong thoughts about the actual role, like the people I've met who were doing that role tend to find contribute valuable things. I do think that the label for that role is maybe a little off. But also as I was talking through that, I was just thinking about how we don't have a lot of words for what we do that aren't borrowed from other industries.

Right. Engineer, architect, developer, those all mean different things in other places. I have friends who are in development that don't ever touch a computer because I think it has something to do with raising money. I don't know. I think the closest thing I could come to a word that describes what I do that is unique to our industry but programmer, but I feel like that's really only a part of what we do.

Absolutely. Just like everything else in software, it's really hard to name these things. It was a keynote. I'm going to keep doing that just for the rest of my life from Sarah May that proposed the metaphor of a group of theater professionals putting on a show is a much better metaphor for what we do in software development. But since I had to use the phrase theater professionals putting on a show, it's not exactly pithy enough for especially a job title and not everyone shares that experience or has a conception of what that even looks like.

That one, well, it fits the situation better is not as good at communicating an idea. For those who were not there to hear your keynote, your keynote was a keynote of keynote. You went back and watched was it 10 years of no more than that, 20 years of RailsConfs every single keynote and then summarize lessons learned. So now- They're just in there. Yeah, you're going to have this probably every episode you're on for this show.

You're always going to have in your back pocket. So there's a 2009 keynote from RailsConfs that addressed this topic. Your whole life is a keynote of keynotes now. Yeah, I've been that person's like, you know, you should go back and watch this keynote for months at this point. I have watched some of the ones you've recommended that when you've got, I think I'm really enjoying the benefits of having someone curate the keynotes for me.

Thank you. I wrote a jest with links to all the videos and then my kind of not to miss the list at the bottom. We can include our link to that. Have you ever tried to debug an issue in production while switching between your error tracker, log viewer and APM tool? Maybe you know how painful it is when you can see the error but can't find the relevant logs or when you see slow performance but it can't connect to the root cause.

Scout monitoring is all in one platform, built to make your life easier. With log management, performance tracking and error monitoring coming soon, all of your data will be together at last. We'll go from bug to fix in one place. The result? Less context switching, faster debugging and monitoring that actually helps you ship code instead of distracting from it.

No DevOps team? No problem. Scout works with your existing stack and gives you insights in five minutes, not hours. From bug to fix in one place at ScoutAPM.com. You know, I think I know what needs to come here.

I think we need a tier ranking. That's tough but it's an interesting idea. I always feel bad putting, you know, ranking something somebody worked hard on at the bottom of something like that. That's fair. That's why I didn't include a skip list because it's like they were skips for me but there was still so much work and energy and passion and everything put into it and dedication that it not only feels bad but also in someone else's context, it might be the most important one to watch.

So that's hard to do. Well, any list that you put together is going to be biased or biased on some negative, right? But it's made for you for your perspective. These are the things that hit for you and the things that missed for you. Exactly.

It's impossible to separate yourself from a list like that. I don't think I said that at the beginning of the keynote but I kind of wanted to. Anything that I talked about was always going to be from my perspective and you're not getting the truth of whatever keynote from what I'm saying because it's what I took away. Sewing bias isn't a negative word. It doesn't mean the same thing necessarily but when you were cutting something on the bias or sewing something on the bias, you are taking the fabric and basically rotating it 45 degrees so that the grain of the fabric goes 45 degrees instead of up and down.

And so from that perspective, it just feels like an angle, a perspective and not a negative prejudice or something. There's my bias, there's your bias, there's everybody's bias and they're all interesting and different. I think you can say in English that you have an angle on something. Would you say that the positive or negative connotation to say, oh, Sally's got an angle on this? I feel like I'm most likely to use that in the phrase like, oh, that's an interesting angle to look at it.

Okay. So then you're looking at it specifically as a perspective. Yeah. I don't feel like there's a negative or positive connotation to that, just sort of a variation. It's a neutral statement effect.

Well, another maybe neutral statement effect, although one that I am biased in favor of. I'm excited to have you both join the show but that's not it. We're making a lot more changes. Yeah. One of the big ones is that we're going to be moving to more of a season based model.

So instead of just sort of constant three-minute episodes, we are going to be sort of building them out in a little bit more of a cohesive way for in like 12 episode groups. And then maybe taking a week or two break and then building out another 12 episode group. Within those, we're still figuring out exactly how we want to structure them, but we do want there to be a little bit of variability. So we're always going to try to have a guest episode in the middle and some kind of recap episode at the end. We might introduce some more sort of rhythms over the arc of a season as we keep experimenting. But that's sort of the direction that we're moving in.

And I want to point out that, as Joelle said, that's going to be a week or two break in the middle. It's not going to be like some of this new prestige TV where you're going to have to wait four years for the next season or anything like that. So don't worry. You'll still be getting your bike shed regularly just with a little time to decompress between. Within that structure, Salty, you want to talk a little bit about how that's going to look like with now three hosts on the show? Yeah, absolutely. So we're all here together today,

but going forward, we're going to be rotating. So there's going to be two of us talking about something at any given week. We don't necessarily have a strict structure for that yet. It'll sort of fluctuate depending on schedules and topics. But hopefully you'll get to see a lot of each pair of of us. And I think it'll be fun to see how those different dynamics come out.

And the thought for that recap episode at the end, don't really know what that looks like yet, but I'm very excited to see because that's something that I've always wanted to be able to do in kind of my work life is to have moments throughout the year where I can reflect kind of embed some of the learning a little bit deeper through reflection. And I always love obviously talking shops. So talking about how that is going to affect our work and methodology is super interesting to me. But I am not one who builds habits easily. So I have two accountability buddies here and many more accountability buddies out there in podcast land who are going to help me keep up this habit and see what all we can gain from this sort of new feature in the way that we learn and the way that we think about it.

I always love the recap episodes that we did on the bike shed was definitely typically at the end of the year where we would look at a lot of different things. So maybe talk about some things that we accomplished, things that we've learned typically we would share maybe an article or a book that we'd read that was particularly impactful and talked a little bit about why that was sometimes we've talked about what is the one thing that you found yourself like linking other people to constantly in the last period. Sometimes it's a little bit because that's on your mind. Now you see that problem everywhere. You're like, I've got an article for that. Sometimes it's

just because you're on a project where it's like, Oh, I'm dealing with a lot of times on problems and I've got the article for everybody. But I really do like that sort of recap of what was impactful for you. How did you grow? What are maybe some things that you've learned? We also, I think in a lot of episodes will like encounter thing be like, Oh, this is cool. You're experimenting with this thing.

We should check in with you later to like hear how that went. And we don't always close that loop. And so I think that recap episode is a great place to sort of come back and say, Hey, you were experimenting with this new tool that you weren't sure about. Are you still using it? Is that working for you? Hey, Sally, you were working on that open source library. Where's that

now that we it's been 12 weeks? Yeah, that's definitely a accountability. It's definitely going to be useful to have this podcast and that people I'm making it with and the people listening to it as accountability is for things like that. Now that I've told you about that, that gem, I've got to follow through. So you can look forward to sort of rotating pairs of us over a period of 12 weeks, then a couple of weeks break and then picking it up again for another season with the occasional guests. If you've been a more recent listener of the show in the past six months or so,

it's always been me and a guest. But traditionally, the bike shed is less of an interview show and more of a personality show where you have a consistent set of hosts and you get to hear them interact on variety of topics. So we're going back a little bit to the roots of the show for that. This is sort of a more permanent set of people that you'll hear on air. You'll get a better chance to get to know me, get to know Ajay, get to know Sally in the coming months.

Yeah. Can I talk about the other exciting thing? Yes, let's hear it. We are going to try to do some video. We are recording video today. We'll see if it turns out to actually be something we

share with you today, but bear with us while we're learning. But we're excited to sort of connect with you a little more that way and to see our faces while you hear our words if you choose to. In case you didn't know, the bike shed is already on YouTube. We just published the audio there. If that's the place where you like to get your podcasts, but now we're actually going to start doing videos. So you get to actually see our faces. I'm going to have to clean up the messy craft room

that I code in for that though. We're not going to promise pristine sets here. No, this is a podcast after all. So yeah, welcome, Ajay and Sally. It's exciting to have you join the show as permanent members of the cast. And all three of us are excited to share with all you listeners a little

bit about what we've learned along the way. So it is my pleasure, my privilege to ask you for the first time as permanent cast members. What's new in your world? So recently I have been diving really deeply into the OASP Top 10. That is a list of common vulnerabilities or attack factors for web applications and remediations or hopefully preventative in the first place steps that you can take to make sure that your application is more robust against those different factors.

It's something that I've had, I don't want to say casual awareness of, but it's been a little more knowing that list and knowing what you have to do as a developer. But I have had a spark of interest in going really deep and kind of seeing not only where those come from, what they all mean, what are the standards that are attached to them, what is some of the maybe more specialized tooling you can use to learn either how people are exploiting them or maybe try some of those out on some apps running locally. So you get the mindset of how that's going, but I've really wanted to dive in a little bit more to the security side of things. I've often thought that security is one of those things that's an entire specialty and a very important specialty in and of itself. And so it's often best to defer to the people that spend their entire career working on this sort of thing because it is such a vast field and important field. And I've become a little more interested in

getting closer to being one of those people, probably never going to be all the way a security researcher, but really knowing a lot more of the nuts and bolts and the ins and outs of what we need to do as application developers. I think one thing that's really nice about that is we have sort of the room to pursue particular interests within the sort of entire world of development topics. And what that happens then is that we naturally develop a set of sort of internal experts on a variety of things. Everybody's expected to have a sort of base level of understanding of security. We don't want to be creating base security holes in the work that we do. But some of us have a particular interest

in security and then go really deep and then we can lean on those people when we have trick your situations to work with. So even though you're not necessarily booked on a particular client, a thought developer who has a security question might be able to turn to you and say, hey, can I get some of your expertise on that? And that's one of the things that I think is really beautiful with the sort of consulting agency format is that even though you have one or two or three thought developers working on your project, there's sort of a whole organization behind those developers. And we have some of that other expertise we can pull in on more ad hoc basis to support us. I really like that too. I think there's lots of areas where people have specialized that are

super helpful. I'm particularly thinking of we have a growing number of people actually who are really interested in accessibility. And so on every project I work on, even if there's not one of those people on the project, we have them to reach out to and to help support our peripheral knowledge of accessibility. And we have a mentality of sharing our learning and learning in public. And so as folks are doing these kind of more specialized journeys or even less so, if someone discovers a nice interesting piece of information, we'll often share it across the company. So you're

almost getting like a minor focus in what some other people are going really deep in because as they're uncovering interesting things, they're just going to be sharing it with the group anyway, not to get all sales pitchy. But I think that's one of the strengths of ThoughtBot is that when you've got a couple of ThoughtBot developers on your team, you've really got the whole group experience of ThoughtBot sort of at their fingertips. That's really exciting. I look forward to sending you more security questions, Ajit. I look forward to our recap episode where I tell you how this went.

Yeah, I will be checking in on you. Sally, what's new in your world? Well, I've been internally maybe a little notorious for my resistance to do heavy front-end work. I think I mentioned this before, but I'm working on a project now where I cannot avoid React, which was frustrating at first. But this week, I suddenly realized that I was enjoying working on React, like enjoying figuring out how to do some complicated interactions and even enjoying figuring out how to make as close to a pixel-perfect match of the design as I could. So that's been kind of

exciting because I haven't been sort of intentionally anti-fronted. It's just been a lot harder for me. And so it has felt really good to start to build their skills and get to a point where I can go, oh, I think I actually know what to do here without having to read all the documentation again and having it come easier and easier. Not to say I would sign up for a full-time React-only job, but I'm not going to pout quite as much next time I have to do it. What do you think caused the change for you?

Was it just that you sort of finally built up enough base knowledge that all of a sudden you didn't feel like you were struggling as much? Did you just sort of like, is there a mental model that clicked and all of a sudden you're like, oh, this is elegant and I love it? I wouldn't go that far in the past because, you know, partly because of what we just talked about, where we have such a deep pool of knowledge among thought-bought people. I've been able to sort of sidestep doing a ton of React and there's always been someone sort of on the team who I could pass off those bits to and do those parts that I found were fun. And that just wasn't possible in this situation.

There was too much to do and we're also intentionally trying to get everyone on the client team and our team to sort of be able to do full-stack top to bottom. So I think what clicked for me was sort of part of it is just practice just doing it over and over again. Part of it was also reviewing a lot of PRs that had to do with React. At the beginning I would just skim them and be like, well, I guess I understand what this is trying to do. But, and now I've gotten to the point where just it really is just practice where I can go, ah, this looks a little off from what I would expect or more often, oh, that's a new way of doing this and I leave a lot of PR comments saying this is, I just want to learn why are you doing it this way? What's the difference between that?

So asking a lot of questions, looking at a lot of stuff, reading a lot of documentation. We're also at a point where like this project is shifting technology stacks, so we're making a lot of decisions internally. So it's not just, well, this is what the project is using, so we're going to move forward. There are lots of moments where it's like, which tool should we use? We have two different teams on this project approaching things in different ways and we want to converge. So now we're going to have a conversation about what the different patterns do and what

the pros and cons of each of them are, which has been a great opportunity to sort of understand and start to see the patterns and see the purpose of the various pieces of it. I feel like just that side, that like negotiating two different teams with different ways of working, that could be a whole episode in and of itself. And maybe that's one that we'll do at a later point, but building software is not just writing code, it's writing code in the context of a team. And sometimes that team disagrees. Yes, sometimes they do. And there's very rarely a, well, this person is right and that person is wrong,

but because there's just different perspectives to it and different past experiences and priorities. Thankfully, everyone on the team is really great to work with and interested in making the right decisions for the project and interested in learning and sharing. So these have been really fun conversations in some contexts, conversations like that can get really uncomfortable and difficult. I'm lucky enough to be in a space where we're all coming into it with an open mind and similar goals, which is successful product. It's been exciting rather than stressful.

I'm glad to hear that. Yeah. It hasn't always been that case in the past. I'm interested really quick if either of you have a sort of name for the moment, I think it's interesting, Sally, that you said seeing the patterns as part of this, cresting the hill of being able to understand the front end, because I've always really enjoyed that moment where the things have come together enough for you, the crystallized enough for you, that you can kind of into it and you have an intuition or a mental model about how things are working, but you might still not be proficient in the area. And sort of my familact, that's the grouping of terms that might not mean anything to people outside of a group, but have come to kind of form a shorthand for, in this case, I think specifically a family, because my wife and I use the term seeing the pattern for that kind of moment coming from juggling, actually, because if you're trying to learn a new juggling trick, you try to throw it and at first, even if you're a seasoned juggler, it just looks like chaos in the air. You can't even tell where the balls the clubs

are supposed to be going, but eventually you can see the pattern and you can't catch it. You can't throw it right. You still can't do the trick, but it now makes sense. There is some kind of intuition about what's going on in the air. And I've never had a better term to describe that moment. And I

was wondering if either of you have a label or an idea about that particular concept. I think I've tended to call those maybe like aha moments or eureka moments, just that moment where the light bulb turns on. Or sometimes I imagine it's like, you've got a bunch of little connections between one or two concepts and they're sort of all floating around your brain and you find one nexus that actually brings them all together and all of a sudden you've got one giant net of connected ideas. And it's when you drop in that one piece that connects everything else that then everything lights up. I think for me, it's less often a single moment where things start to make sense and more often a moment where I realize that has happened. So it's not like I'm sitting here

and going, ah, now I get it. It's more like I've been practicing and trying and then suddenly I realize like, oh, I've gone a whole day without feeling super frustrated and angry at this. Or, you know, I've realized that this documentation that I used to have to refer to every time, I don't need to look at anymore. I have a similar situation in knitting where I'm working on something that's sort of like a complicated four row repeat where every row is a little bit different. And there's always a moment in the project where I realize that I don't have to look back at the pattern every row. And I can start to sort of just go by memory and instinct.

I need to think so. What's new in your world? I've been really excited recently about part of a language specification. This is the rock language. And the way it has sort of defined its language is that it has, it's one of those like purely functional type languages. And it has sort of the core of the language. And then separately,

all of your sort of side effecting things, interactions with the outside world are tied into what it calls a platform. And so a platform is just a model that you pull in, but it sort of determines when you compile sort of what is the output of the program going to be and how does it bind to whatever it is in particular environment that you're running in with the idea that you can write rock code to run the browser where you're emitting JavaScript, you might not have access to the file system, but you do have access to making network quests, but only in an asynchronous way versus maybe if you're running a rock program on a Windows machine, you do have synchronous file system access. And you've got access to maybe some different UI window components that you don't have access to in a browser. And so all the things that are sort of environment specific are things that your platform has to provide for you versus the parts of the language that are just this is the code part, not the environment part. And what I really loved about that is the very like explicit separation of the two. I feel like we tend to intermix them a lot. And so having a

very clear separation, it's like, oh, yeah, that makes sense. You have code parts, you have environmental parts. And if you're trying to port your code to a different environment, then you might have different things you have access to or the concurrency model might be different or things like that. And then also, because it's a purely functional language, this connected with me, a little bit of functional theory, the idea that the pure functional parts are the parts that are effectively platform independent. And all of the non functional parts, the side effects, those are the parts that are built into these little platforms. So that was one of those, I had one of those aha moments reading

that being like, Oh, no, that separation makes so much sense. Have you experienced like, have you been playing with it enough to have been able to run the same code on different platforms and sort of see how it varies? No, I have not. And I don't know the ideas necessarily to make all code cross platform, because by design, different platforms expose different primitives. I think in theory, that's nice is that the compiler could tell you the type checker could tell you, hey, you're trying to like do file system access, but this platform does not provide that. So just by swapping out the

platform, you could get a list of errors that tell you all the ways in which your program is incompatible. That's nice to get for free. But I'm thinking more in terms of the mental model of having a weirdness about the platform in which you run your code. I think very often we just sort of think, Oh, I'm writing Ruby, therefore, I get to do the Ruby things. And like, some things like innumerable, that's a Ruby thing that's a Ruby construct or blocks, that's a Ruby construct core to the language.

But the details of how we do file system access, that might vary in different environments where you're running Ruby. Have you found that that separation being that a ham moment for you has changed the way that you see or work with non-rock code? Yes, I think particularly when I think about JavaScript, because you can run JavaScript in the browser. And there's a lot of things we think of sort of core JavaScript, but they're not really core JavaScript. They're browser APIs, things like the DOM. But even you might talk about the sort of fetch API for making requests, that is particular to

the way the browser works, because requests have to happen asynchronously in the background versus you're running on node. And node JS is going to be running in a totally different environment with a different set of capabilities and limitations. You're still writing JavaScript, but the way that you do IO might be a little bit different. The way you write to files, now you can write to files, and the way that you can't in the browser. The way you do network requests might be a little bit different.

The way you do concurrency might be a little bit different. And you'll just throw maybe a third platform in there. I was on a project last year where I was working on a browser extension. And what you have access to and the kind of things you can do in a browser extension are slightly different than what you have access to and what you can do in the context of just code on a web browser. And so the sort of the underlying primitives are different. And if you have sort of in your mind

or I'm writing JavaScript, I know how to write JavaScript, I can just do this and aren't thinking, what is the environment my JavaScript is operating in? You can trip over yourself. And so I think having that mental model of separation between code and platform is a thing that is going to really serve me as I sort of move forward. I love those kind of insights that you can get from experimenting in a different realm that has different sort of foundational conceptualization of itself, its environment, how it works. It's almost like I learned more about speaking English in French class than I did in English class, that sort of thing. It's the differences that can tell you more

about your sort of native perspective. Yeah, it can help you sort of identify the assumptions that you've made and the defaults you've come to expect is that maybe are not as globally applicable as you thought they were. Should we wrap up? Let's wrap up.

Frequently asked questions

How long is this episode of The Bike Shed?

This episode is 42 minutes long.

When was this The Bike Shed episode published?

This episode was published on August 26, 2025.

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.