Skip to content
501: What makes for good technical writing? episode artwork

Jun 2, 2026 34 min

501: What makes for good technical writing?

from The Bike Shed Hosted by thoughtbot

Sally and Joël get technical as they lay out their thoughts on blog posts. Our hosts pick apart what makes a good technical blog post, why consistent terms are more important than you might think when communicating with your audience, and how to improve your own writing to ensure your reader remains engaged. — There’s still time to secure your place at thoughtbot’s upcoming UK meet ups over the next month. London Tech Leader Meetup - Tuesday June 23rd Brighton Tech Leader Meetup - Wednesday June 24th Brighton Ruby - Thursday June 25th Evolve - Friday June 26th Your hosts for this episode have been thoughtbot’s own Joël Quenneville and Sally Hall. 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

501: What makes for good technical writing?

0:00 34:27
of matches

Transcript Auto-generated, may contain errors

Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at Thoughtbot about developing great software. I'm Sally Hall. And I'm Joel Kinville, and together we're here to hear a bit of what we've learned along the way. So Joel, what's new in your world? Fun random thing that happened recently is my town puts on something called Porchfest, which is basically all of the local people who are in bands go out on their porches on the same day and play music. And you get to just wander around sort of from house to

house and it's just a big party in the streets. That sounds like it would be very fun for people who are not me. Do you play music or did you observe music or both? I observe music. And I'm not a huge band person. I'm not like, especially, you know, these are

all sort of the same style of like kind of garage band type thing. Occasionally you find somebody doing something really different. So they're not all like aging millennials with guitars? They are mostly aging-wise with guitars. Yeah.

But there was a woman with a banjo at one place. It was pretty fun. That's awesome. There was a place that sort of took over a cul-de-sac and like a fiddler and a collar. We're doing concert dancing.

Oh. That's not okay. I take it back. I would enjoy some of this. For those who are familiar who are the audience, concert dancing is a, I guess, a traditional age form of dancing where it's, there's some of those sort of calls out to removes and you do different things. It's not exactly partner dancing, although I guess there are

partners involved, but you switch around and you do different things. Yeah. I feel like it's sort of somewhere between like the old-fashioned dances you might see on a show like Bridgerton where it's like 10 or 12 people and they're all doing something and they all seem to know where to go, but it doesn't necessarily make sense. And squared dancing somewhere between those is my next spring for concert dancing. Yeah. I guess squared dancing is probably the closer example there.

Oh, there was a wedding. Somebody just did a wedding on their porch and had like an audience in the street watching them. That's cool. It's definitely an affordable and straightforward way to do it when I hear that. And you get a lot of people that cheer you on.

Yeah, absolutely. Cool. So a lot of random stuff. It happens every spring. It's just fun to wander around the town.

It's a big party. How about you? What's new in your world? Well, a few weeks ago was, so I have my kids are both seniors in high school, so we're doing a lot of the last insert, everything here. And one of my kids has been really involved in the theater program. So the last theater performance was a couple weeks ago. It was

Mary Poppins. And I got more involved than I usually do and spent like the whole week leading up to it, helping with costumes, which was a fun experience. It was really, I don't know, it was like a different kind of sewing than I usually do because I like to craft slowly and carefully and like undo something and redo it until I get it just the way I want it to be. And there's no room for that when you're making costumes for 42 high school kids in a play. There is, can we fix it with a safety pin? Yes. Okay. And let's say

a safety pin. It's very rushed, but in the kind of way that it's been really fun. So it was really nice to just sort of use my brain in a different way than thoughtful coding and review. Instead, it's like, make this skirt fit, this person, use whatever you can have. It just needs to not fall off and look okay for my distance. It's kind of not the way I've

done really work day to day, but a really fun switch for my brain. It feels like there might be a bit of a metaphor there for some types of software work as well. Not everything has to be the perfect craft polished thing. Sometimes you do just need to have it look good for my distance. Yes, that's true. It's sort of like a hackathon

but for costumes. Yeah. Yeah. I'm a little sad that I didn't like start getting involved to that degree with the costume stuff earlier in my kids high school career because I'm not the kind of parent who is dedicated enough to help next year when I don't have a kid at the school anymore, but right, I do regret the missed opportunities to do it in the past. Just need a little bit of self interest. Yeah. Yeah. My niece will probably be in that

theater program in 10 years. So, you know, I'll tell them and help out again then. I feel like the sort of quality volume trade off and like finding the right level of that is a thing that we have to navigate constantly as consultants at that bot based on our particular clients situation. Yeah. But an area that I think that I've been trying to push more on the quality side recently has been the quality of our technical writing. That's a good point.

Yeah. So, things like the blog that also just better awareness around things like documentation. And again, there's always trade offs there. Yeah. I think that could even extend to like issues and tickets for work to be done. That's like writing too. Yeah. What would you say

is we're off the top of your head or things that you look for in technical writing? And maybe let's sort of scope it a little bit more tightly. What makes a like a technical blog post that you read feel like, oh, this is really good as opposed to could there's something interesting here, but could use and polish. I think, and this is something I know you've talked about before, but like keeping an audience in mind for when you're writing, who am I writing this for? And then having a good understanding of like, what do I expect the person who is reading this to already know? And what do I need to explain? Right as far as background? And

I think taking that a bit farther, maybe going a little over, you know, if you're going to air on that border going more towards explaining a little more rather than less, I get very frustrated when I'm reading a blog post or some other writing. And I'm like, I think that this is interesting and probably relevant to me, but there's a foundational idea that I'm not familiar with. And I have to go do my own research on that before I can understand this writing. So, you know, knowing when to define something or link to another resource or something like that for the audience that you're writing for. Right. How I'm going

to define a background idea is going to be different if I'm writing for other senior developers versus founders who may be non-technical. Those are going to be different background types. I'm very aware of like sort of what your assumptions are in terms of what people already know. Exactly. Assumptions. And I feel like that's it's a hard balance between like,

not infantilizing your audience, but also making sure to include them and making sure that like people from a wider range of experience and knowledge can access what you're writing. And also at some point, you can't just explain the foundational ideas behind everything because Right. I can't start with like the proof of Y1 plus one equals two. That's, uh-huh. I'm going to assume some things. Let me talk to you about why it's good for a class to

have a single responsibility. But before we get there, let me tell you about molecules, a matter of behaves. And then we'll talk about Silicon and then, If you're new here, here's a link to something else I wrote about the origins of the universe. I like the idea of keeping things scoped by linking out for other foundational concepts. It's like the third notes of the blog post. Yeah. Yeah.

Although I have actual funets too. The price of entry for this particular thing is you need to know these five other ideas. I'm going to sort of assume that you know them. But if you don't, here's a place where you can go read up on them as opposed to like, if you don't tough luck, figure out on your own. Yeah.

Sort of like supporting and respecting your reader at the same time. Because I guess that like a flip side to that is I appreciate when blog posts have a relatively tight focus. They have an idea and they're focused on that idea. They're trying to get you to follow the path that leads you to that idea. And they don't get sort of lost on all the other tangents or other random things that we're in the authors mind at the time.

That makes it really hard to write. I find a lot of times my first draft is like four blog posts. And then I've got to, you know, break it down into like what actually makes sense as I go here in piece of this or what doesn't need to be written about it all. And it's just my thoughts. I think that's part of the reason why I review by someone else is often helpful because they can be like, okay, I got lost in a whole tangle of ideas here.

It sounds like you're trying to say this. And if so, the second half of your blog post should just be your main content and you can just drop the first half. Yeah, it's good if someone else identifies like, this is the part of your writing that excites me and interests me. Focus on that to these other parts. Maybe not.

I do feel that for my own writing oftentimes it is that second half of the rough draft that ends up becoming the article. But like working up to the thing I actually want to say, I often spend way too much time in that working up to it and be like, well, this other background thing and this other idea and then actually like get to the thing I want to say. And it's like, you just meant way too long to get there. Like compress that first half of the blog post into one intro paragraph and then just say the thing. Yeah. Another thing that I find very important in all technical writing, but definitely in

blog posts is consistency with terminology. Right. So if you're writing about something that has to do with classes and you're working in Rails and you sometimes, or if you're writing about models and you sometimes say class and sometimes say model, like those aren't interchangeable, they might feel interchangeable in your concept of the thing. And for what you're writing about it might not matter which one you're using, but if you switch back and forth between them, then I can't tell if you're talking about the same concept, especially if you haven't like defined the subtleties. I don't like that example very much.

No, I think there's a lot there. The two things that are like sort of interchangeable, not quite or even sometimes fully interchangeable, but you just don't use it consistently or going to confuse people. Yes. One that confused me as a junior developer for the longest time, parameters and arguments. Yes, that's a great example. Yeah, those are slightly different.

And in a lot of cases, they're interchangeable, but it's still confusing if you don't stick to one. Right. And so like, I'm reading a thing like, oh, this is how functions work. All right, let me figure out how to, you call this thing an argument earlier. Now it's a parameter. Is there a difference?

Do I need to, but you don't define the terms? Do I need to look it up? It really confused me as a brand new programmer. Yeah, absolutely. Yeah. So like, choose your terms, stick with them,

keep that focused and scope to two. Sometimes I think that you can hit maybe the opposite form of that as well. Well, you'll use some terms, but maybe you don't define them. So use them consistently, but you don't necessarily explain them. And it's not always obvious what you mean by that. Yeah, yeah. It can feel like you've wandered in in the middle of a conversation.

Or you'll have a term that you use, you know, just just the one term across your article, but you use it in slightly different ways because it has maybe two definitions or three definitions that are all like similar, but like maybe have different connotations and you don't necessarily call out that distinction. Yeah, I could see accidentally doing that with the word enum. There is a blog post that one of our colleagues at Thought wrote that I think is titled like enum versus enum versus enum. Yeah, just because the word means so many different things. And he was really confused and had to do a deep dive on it. And eventually I should run

article about this. Yeah, it's like the there, there, there, of programming. I think another thing that I find really helpful in technical writing is understanding the why. If I find a post that's like, here's how to switch from this tool to that tool. But there's nothing in there about why I would switch from one tool to the other or what each tool is better for. It's just out of nowhere here

is a way that you can do this thing that you've never imagined doing before. And I'm not going to tell you why you would do it. It's like, okay, but this is like, I feel like I'm missing context and can't easily like slot this into my mental view or framework of the things that we're talking about because I don't understand the motivation or like the goal, the goal really, I think having a clear goal I think is helpful. I think related to that, I recently wrote some internal guidance for public authors and I built a sort of framework of archetypes for sort of common types of blog posts that we tend to write. And each of those tend to be geared towards an audience with slightly different needs and motivations. They have oftentimes sort of their own language, way of structuring

things, way of having examples, but they're often based on a fundamentally different motivation. And so how you'd express that is going to be totally different. And your goal is the author is often very different. The four sort of high level archetypes are how to, which is really geared at solving a problem. That's the sort of thing where you get stuck, you Google, you find an article and you just want to be like, I have this problem. How do I fix it? Which is separate from an explainer,

which is all about sort of understanding the why behind certain things can be a little bit more theoretical. But how to is very concrete tends to be very short, has a small code example that shows the whole thing. You can just copy paste that into your code versus an explainer might show different variants. It might dig into some of the details behind. It might show more code snippets, things like that versus sort of what I've called the walk along or the narrative, which is a little bit more of a, hey, here's the thing that we did. Let me walk you through the story. It might be a

sort of debugging horror story. How do we eventually get to understand this particular bug? Or it could be a just here's a cool thing that we built or here's a cool thing you might want to build. Let me walk you through every step that we went through there. And it's not a how do I build this thing. It's a

let me look over your shoulder and see your process. Yeah. And so in that case, you might show a lot of incremental variants of some code. You might even show some code in like diff format. And the goals are totally different, right? Someone who's looking at a walk along has totally different amounts of

time to sink into your blog post than someone who's looking for how to. And the final fourth archetype is just the classic or persuasive essay. Here's a practice that we think that you should or shouldn't do. And here's why. What are your thoughts on sort of including a why in the how to? Oh, the why

this solution is the solution to your fix or to your problem? Or even like, what the problem is that you're solving? Yes, yes, you have to define the problem before you solve it. But it's generally very sort of short. So it's a hey, you encounter this error message. Here's the solution for it. Or

you run into this sort of challenging edge case with, I don't know, active record. You need this line and initializer. Or you need to structure your objects in this way. Or you need to use this gem I just made in here. So you use it to solve to do that thing. Sometimes you can have even a

particular topic or problem. And you could write probably an article from each of those four archetypes. And they're all examining a very different aspect of the problem for a different audience. And they're all valid articles. They could all be published. So it's oftentimes kind of dealer's

choice as an author. It's a who's your audience? What are you trying to say to them and then pick one of these that fits the message you're trying to say. Do you have a particular archetype that is your preference for writing and then separately for you reading? I know that I've got some, but I'm interested to hear yours first. I love the explainer. As a writer or a reader, both.

Honestly, both. Because I think I like to grapple with ideas. How tos are nice, you know, from stock or something. I'm just trying to like build a catalog of techniques in my mind. But explainers are my happy place. Conversely, I think the walk along is something that I kind of

struggle with. I find that there you have to go read a lot of content to really get much value out of it. And it's just not the kind of content I find that I engage with a lot. The walk along is the one that I find I tend to write the most, especially in a first draft. But it also kind of feels like, you know, the recipe blog of technical writing. Like I don't need to hear about you growing up in a farm

just give me the green bean recipe. I think that's a I actually put this in the guy that I wrote. It's a common pitfall for how to article. Yeah. Similar to a recipe, you just want the fix and you don't need pages of backstory. But if you're looking for an entertaining story or you want to

get a sense of someone's process, then yes, the story is the thing you're there for. I try to avoid writing the walkthrough unless I know that it's funny. You know, if it's just kind of like, here's the story of how I got here. And it's kind of a dry narrative of things that happened to me. But I could, you know, I could just get to the point. But I like them both writing

and reading them more when it can be sort of funny or metaphor or something like that. But I think what I prefer to read really depends on again, what problem I'm trying to solve. A nice pithy how to is always delightful, you know, just like here's your solution. But I also the like persuasive essays. Sometimes I'm really interested to hear other people's detailed opinions about what the correct approach to something is. And my favorite is when I can

find two opposing ones. I guess one of the like pitfalls of a more persuasive essay is having poor logic. You know, an explainer, how to oftentimes you don't have quite as much of like a heavy to develop an argument. And sometimes I find I'll read rough drafts that people write and like they're they're moving, I think from a solid point, from a solid foundation to maybe a solid conclusion. But the path they take to get there is just not not solid. And it can be really difficult to spot

that if you agree with the conclusion. Yeah. And it can be frustrating too, because it's like, I want to support what you're saying, but the way that you have said it is so unhelpful. Right. Or just will not stand up as scrutiny, right? You can persuade me because I'm already

persuaded. But if you're trying to persuade someone who's on the fence or maybe someone who's even has the opposite position, they're going to look at your argument and be like, here's how it falls apart. And then they're just not you're going to not succeed at what you're trying to do. Yeah, I find that sometimes that can be the result of trying to over convince somebody. Hmm. Say more. Maybe I'm about to do it right now. You know, like you believe it so

thoroughly, but you had trouble explaining exactly why. So you end up just sort of talking around the logic in a way, sort of like desperately hoping one of the things that I'm saying will grab you and make sense. I feel like it's, you know, it's a little bit along the like, I mean, we think the lady Doth process too much. Sometimes it can become clear that someone doesn't really understand the why what they're trying to explain actually works because they're going in so many different directions trying to support it and trying to like prove that this is a good idea. Honestly, that's not a bad exercise and like self awareness, growing ideas for yourself, trying to realize, oh, maybe I don't understand it quite as much as I thought as I did. Yeah.

So that case, you know, your first draft maybe it's just like a thought exercise for like, let me prove to myself that this thing, I believe is true or is the best way to do something. Right. I do find it helpful in my own when I do try to write persuasively to do a pass where I will read it sort of adversarially to be like, if someone was looking at this, who is a bit skeptical of my article and just goes through and at that point, because they're a skeptic, they're going to be sort of hyper-tuned to any sort of mistakes in logic that I make or like, what are the moments they're going to be like, wait a minute, you can't say that. The thing you're saying does not follow from the previous thing, you just did a big leap of logic. I disagree with that.

Yeah. Or what are the moments that they're going to be maybe a little bit lost or like this, I'm not quite sure where we're going with this. What are the moments where they're like, oh, this is just deeply problematic in the way that you structured this argument. That does not do what you think it does. I remember in college, so I was a math major and I remember one of my professors saying that like, an indicator for that sort of argument is the words clearly were obviously.

If one of the steps of the argument is, well, clearly this happens. It's like, well, no, if that was clear, you wouldn't have to say clearly. So I don't believe that. Yeah, you're going to have to show how one thing leads to another, not just state it and then shut down criticism by saying clearly. Yeah. And all of us are going to be too worried that we'll look stupid if we question it to say

anything because he said it's clear. So it must be clear. Sometimes I find it useful to narrow your premise or your conclusion as well. If you're trying to make a statement that's sort of universal to all code bases or whatever, that's really hard to make something that's going to hold true in all situations. Yeah. Although, we love and absolute.

We do humans really want. We don't like it depends. But I think if you can sort of bake in a little bit of it depends or the fairly sort of scope, your argument and say, I find that this sort of approach is the best for this type of code base. Now, that's a totally different argument. And you've also sort of insulated yourself from a bit of a spurious counter argument of like, well, what about this kind of problem?

You're like, but that's not the problem I'm trying to solve. Yeah. So scoping argument is really, really valuable. And maybe taking it one step further and saying, here are some indicators that this solution is not the right one for your problem. So like, hey, this is a great solution.

For a small code base that changes all the time. But if you've got like a huge team, then you're not going to want to do it this way. Yeah. Well, one thing that I like to do is surfacing in a trade off or a series of trade offs. What is the value that you're optimizing for?

Yes. This came up recently in a conversation around factories versus fixtures. And trying to think about, are you optimizing for code readability and modifiability? Are you optimizing for execution speed? What sort of team are you working with?

Is this a team that has a lot of churn? Is this a small team that's been there for 10 years? And so all of those variables are going to change what you're doing. But if you want to argue for a particular approach, you can say, you are optimizing for this style of team and you care a lot about readability more so than speed, although you want to get as much speed as you can within the confines of certain readability. Given this profile, here's how I would recommend that you approach that.

And that's a much more nuanced, but I would say more convincing article. Yeah, absolutely. If you're aware of the limitations of the thing that you're writing about, then I believe that you fully understand it. And I believe that it's really worked for the situations that you are describing it as a solution for. That's also easy to go too far where you had so many caveats that because you're afraid of criticism, that it is all non-falsifiable because you have caviarted it to death.

If you find this bug in this week, the last Tuesday, this is the solution. And that gets to a classic piece of writing advice that you'll hear a lot, which is just trying to write more confidently. I struggle with that one. I'm very good at doing the combative reading of my own stuff that you were talking about earlier. Well, really? How do you know that's true? Are you sure?

That's really like sometimes it is possible for there to maybe be a chance that this thing could happen that I think that maybe we should do. Yeah, and it's helpful for me to like sometimes I have to remind myself that everybody who's reading a thing can, to some degree, keep in mind, that there are caveats and there are exceptions. And this is not universal. So I don't have to actually spell out every single caveat and exception. But the less confident I am about something, the more likely I am to do that. I think something that I've found is that oftentimes

it's best not to have all my caveats in line because then I'm constantly caviating sentences and it just breaks the flow. It's super incompetent. It's often better to maybe do some scoping work at the beginning to say, this is the type of problem I'm applying it to. So don't try to like apply outside of that. And then potentially at the end have a like, here are some exceptions to when I tend to not like to use this solution. And you know, sometimes even it's like, cut all this stuff out,

like you don't need all this extra caviating. But if I am going to do something, I often like to pull it into either the intro or the conclusion. This, I feel like this is making me think of writing advice, like professional writing advice I've heard for women in general, not necessarily technical writing, because women tend to be less confident in situations like this sometimes that right here I am doing sometimes I'm doing exactly a separate writing. Right. So women are often less confident or less likely to write or speak with confidence because of all these social reasons we're not going to talk about right now. And so there's I've read a lot of advice that say, you know, go through your,

write your email and then go back through and take out all of the I thinks that maybe is the I feel that like, if that makes sense, all of that like you can write it that way the first time and then go back through and just delete all of that. They also tell you to delete some exclamation points, but I think you're excited about it. You can leave those in. I love an exclamation point. I probably overuse them, but they're fun. You know, share your passion. Yeah. Yeah. So I'm sometimes hyper

aware of that and just the fact that the context of like writing a technical article as a woman and feeling a little bit of defensiveness, just knowing that honestly, like having a woman's name at the top of an article is going to make some people automatically trust it less or question it more or attack it more. It's hard, but I want to try to write with the confidence of a man. I've heard the phrase, you know, do that with a confidence of a mediocre white man. I'd like to do it with a confidence of like an actually, you know, accomplished man. But yeah, I think that's something that can be really hard for me for writing is like, how do I, how do I come about that? Like, how do I approach

this confidently despite the decades of conditioning that what I have to say is not actually valuable or correct? That might be a whole other conversation. Yeah, the like the social impacts of our backgrounds on how we write. Yeah. And that's our background, our continuing lived experience. Like my experience

is as a woman, but I know that people of, you know, various other kinds of minority backgrounds have probably experienced similar or worse. How do you feel about a variety of like automated solutions that make suggestions on improvement? Like writing tools that would suggest. Yeah, something like Grammarly that might go through it past and be like, Hey, there's a lot of, there's a missing confidence here. What if we drop all of these qualifiers or that sort of thing?

Or, you know, Oh, what if you use an active voice? I think that there's a fine line with those. I think they can be helpful to a point. I also, you know, worry about homogenizing effect where, you know, it just starts to, if you take too many of those suggestions, then all of our writing starts to sound the same. You lose your voice as an author. Right. Yeah. Yeah. I think those tools

can be useful as long as you can, maintain your voice and maintain your point of view and not, not allow the tool to make you doubt the things that you know are true. Yeah, definitely. It's more of a stylistic thing or I guess it could be a structural thing as well. If you're like, Hey, you're making a point here, but it needs a couple of paragraphs like building up to why this point is true because the audience is not just going to accept that on faith. Do you use those tools? I

haven't really gotten into using them yet, but I wonder I have not I've historically relied a lot on self review, colleague review. Yeah, I've played around a little bit with LMS like reviewing, you're ready? Yeah, like point out sort of structural flaws or areas where you think someone might get stuck. I think there's a lot of potential there, but there are also some pitfalls. But if anything, sometimes it's useful to have that as a foil. Yeah. I feel like sometimes the value that I get

out of a conversation with an LMM is not it telling me the right thing to do. It's it telling me the wrong thing to do. And then I argue with it to tell it why it's wrong. And in the process, I self discover the correct solution. I relate to that so strongly. I've been using cursor recently

because I joined a project where they use it pretty heavily and it's a huge complicated project and hard to get context on. And sometimes I will ask cursor to outline a solution. And then I read the trends of my own because it's just it's a lot easier to edit than to write sometimes. It gets rid of that blank page sort of like inertia task initiation block. Also, I just weirdly enjoy being mean to AI. Maybe that will come back to haunt me decades in the future, but I hope not.

You will not be one of the ones who are spared. Yeah, and that's fine. You know what, I don't want to live in a world where robots are interested. There's something about human psychology that we're super attuned to pointing out mistakes that someone else has made. You know, the classic trope of how it's easier to get an answer from the internet, not by asking a question, but by putting the wrong answer out there. Yes. Yeah. Because someone will come along and correct you. Or like me

watching a baking show, I mean, like, my God, you don't know how to make a pet of shoe at all. What are you doing? It's like, I'm gonna make a pet of shoe. I just need on TV, but I know what you're doing wrong. I can tell you exactly what you're doing wrong. Uh-huh. Sometimes that process is helpful

just as a thought exercise. Yeah. Yeah, absolutely. This is making me think I do actually have a draft blog post that is like four times longer than it should be and needs to be broken down a lot and I've resisted going back to looking at it. But I feel like I might be removed enough from it now that I can pretend AI wrote it and come out with a quick lie there. Oh, you know, do self editing, but

with the with the doubt that I have for AI, just the reels or harsh editorial hat on, you're gonna rip the shreds, pull out that red Sharpie. Yeah, delete this whole page. This means nothing. I think this is a good place to wrap up. Yeah. I'm gonna go edit that blog post.

Frequently asked questions

How long is this episode of The Bike Shed?

This episode is 34 minutes long.

When was this The Bike Shed episode published?

This episode was published on June 2, 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.