Podcast Panel

Brittany Martin

Podcast Panel

Brittany Martin

@regularlady

Julie J

@codewithjulie

3 more speakers

See all speakers

#developer-experience-dx

#mentorship

Podcast Panel

by Brittany Martin, Julie J, Drew Bragg, Joël Quenneville, and Andy Croll

The RubyConf Mini podcast panel features a diverse group of podcasters sharing insights on their experiences and motivations behind their shows. Moderated by Brittany Martin from the Ruby on Rails podcast, the panel discusses the importance of community in podcasting and the objectives behind each show. Here are the key points covered during the session:

Panel Introduction: The panel includes five speakers: Joël Quenneville of 'The Bike Shed', Julie J from 'Ruby For All', Andy Kroll from 'Chats in the Cupboard', Drew Bragg from 'Code and the Code Encoders Who Code It', and moderator Brittany Martin.
Podcast Origin Stories: Each panelist shares their motivation for starting their podcast. Julie J started 'Ruby For All' to support junior developers navigating complex topics. Joël Quenneville transitioned into hosting 'The Bike Shed' and is focused on maintaining its conversational style.
Content Approach: The panelists emphasize the importance of themes relevant to their audience's needs. For instance, Julie’s podcasts often tackle concepts she finds confusing, providing clarity for others.
Community Engagement: The discussion highlights the role of community feedback in shaping their content. Andy Kroll believes in actively supporting initiatives like 'Ruby For All', while Drew Bragg reflects on the challenges faced during recordings and the value of open communication with listeners.
Co-hosting Benefits: Multiple speakers mention the advantages of having co-hosts, which enhances the dynamic and engagement in podcasts, a sentiment echoed by Joël who recently welcomed a co-host.
Handling Technical Topics: Joël discusses creatively addressing complex technical subjects through engaging discussions and informative content, while being mindful of the limitations of audio formats.
Listener Participation and Feedback: The panel acknowledges the significance of listener feedback and responding to suggestions for future episodes, illustrating the fluid and evolving nature of podcasting.
Final Thoughts: The panel concludes with expressions of gratitude for the community and the opportunity to share knowledge and experiences. Participants are encouraged to voice their thoughts and be part of the vibrant podcasting ecosystem.

Overall, the panel captures the spirit of collaboration and support within the developer community, underscoring the ongoing journey of growth and learning through podcasting.

00:00:12.620 Welcome to the RubyConf Mini podcast panel! This is a fun tradition we've started with our podcast panels. On the count of three, we're all going to yell 'Mini' and clap together so that my editor knows our audio is synced up. Ready? One, two, three, 'Mini'!

00:00:24.480 Nice! We are recording live from Providence, Rhode Island, at the RubyConf Mini podcast panel. Thank you all for being here today. I’m excited to introduce our panelists. Each of them will share a phrase they commonly use on their podcast so that our listeners can recognize their voices. From 'The Bike Shed', we have Joël Quenneville.

00:00:43.440 Hello, everyone! From 'Ruby For All', we have Julie J.

00:01:02.399 Hello! From 'Chats in the Cupboard', we have Andy Kroll.

00:01:13.799 Hello, everyone! And from 'Code and the Code Encoders Who Code It', we have Drew Bragg.

00:01:21.000 Hello, and welcome to another episode of 'Code and the Code Encoders Who Code It'. I’m your moderator, Brittany Martin from the Ruby on Rails podcast. To start off our discussion, what is your developer origin story?

00:01:38.040 Before we dive in, I’d like to cover a few points. First, we are incredibly grateful for the opportunity to take the audio feed from this session and post it as a podcast. This is a love letter to our listeners who couldn't be here today. Secondly, I’ll direct most questions at specific panelists, but I encourage everyone to chime in if they wish. Please raise your hand!

00:01:53.280 Speaking of which, we will also be taking questions from you in the RubyConf Mini Slack channel under the '#podcast-panel-questions' channel. Please post your questions there, so our panelists can volunteer to answer them. Lastly, this is the first time a podcast panel is part of the main agenda for this conference.

00:02:12.480 I'm seriously grateful to Gemma, Emily, and Andy for making this happen, as well as Paul, our editor, who works hard and brings a lot of magic to make these panels sound great. Thank you, Paul! Now, let's jump into our first question.

00:02:25.319 Julie, as our newest podcast on the panel, can you tell us why you started 'Ruby For All' and how the community reception has been so far?

00:02:37.680 Thank you for the question, Brittany. I started 'Ruby For All' because, as a junior developer, I was listening to many of the Ruby podcasts, which are fantastic, but the concepts often went over my head.

00:02:44.720 Many podcasts covered concepts that were challenging for me, which made it difficult to relate. I wanted to create something that would help other juniors feel included in the community. I met Andrew at RailsConf, and he graciously offered to co-host, which led to the creation of 'Ruby For All'.

00:03:09.480 As for community reception, it has been great! We've received a lot of positive feedback, with many listeners expressing how much they've enjoyed it and found it helpful. We’re always open to feedback, so if anyone has suggestions on how we can improve, please let me know!

00:03:21.360 Joël, as someone who has taken over hosting duties from a previous podcast host, can you give us some insight into how that transition occurred?

00:03:54.239 Steph Bakeri, the former host of 'The Bike Shed' along with Chris Tumi, was looking to transition out. We were collaborating on a client project, and I was sharing a lot of ideas for potential podcast topics. Eventually, I got invited to the 'Bike Shed' Trello board, where I could directly add ideas.

00:04:17.220 So when it came time to find a new host, I had some inside track on the process. I was thrilled to take on this role, and I’m excited about the direction of the show.

00:04:40.259 That's a great segue into a follow-up question. How will this new era of 'The Bike Shed' be different, and what will remain the same?

00:05:10.299 One unique aspect of 'The Bike Shed' is that it’s a conversation show rather than a traditional interview format. It features two people discussing interesting topics, allowing the audience to be a fly on the wall. This conversational style is a key component of our show's identity that I want to preserve.

00:05:40.259 On the other hand, I’m passionate about visuals and diagramming, and I plan to incorporate those elements more into the show. Recent listeners have noted my excitement about dependency graphs, so I'd love for attendees to come up and discuss those with me.

00:06:00.180 Andy, what is your goal for the podcast 'Chats in the Cupboard'?

00:06:20.220 'Chats in the Cupboard' started as an excuse for me to catch up with Vedathi, who lives in Portland while I’m in Brighton. The time difference can be challenging, and it’s always great to have those conversations and stay connected more often.

00:06:52.740 We wanted to create a space for those interactions because many of us are conference friends and see one another only once a year or so. Generally, I wanted to explore interesting topics with someone I respect, and Vedathi is incredibly smart, so I wanted to learn more from her.

00:07:10.200 That sentiment resonates with the community, Andy. By the way, why are you personally sponsoring 'Ruby For All'?

00:07:46.299 The response to 'Ruby For All' has been amazing, and I believe it represents a broader mindset in the community: taking responsibility when we can. As a developer, I can cover the editing costs for the podcast for a month, and if we all took similar action, imagine what we could accomplish.

00:08:13.260 This event exists because Gemma wanted to create it, and she has made it happen. So my challenge to everyone here is: if you see a need in the community, step up and fill it, as it’s not as difficult as you may think.

00:08:40.740 Brittany, what are your thoughts on the nickname for your podcast? Can you help make it sound cooler?

00:08:47.100 Well, you’ve already given it a nice nickname by calling it 'Code Encoders'. That’s also our Twitter handle now! Our first episode was released in February, and since then, I’ve learned a lot about what it means to produce a podcast.

00:09:11.700 I’ve realized that I need a co-host to keep the dynamic going because it can feel lonely recording solo. Plus, I've learned that having a better process for securing guests is essential.

00:09:36.840 Through luck, many guests have approached me to appear on the podcast, but I know I need a more structured approach moving forward. Despite recording over 200 episodes, I still get nervous before each episode, but once we start rolling, I enjoy having a great conversation.

00:09:54.720 This nervousness is something I want listeners to know is completely normal. So if you’re thinking about starting a podcast, you’re not alone in those feelings.

00:10:22.680 Joël, I see you nodding your head in agreement about finding a co-host. What has your experience been?

00:10:51.840 So, I recently brought on a new co-host, Stephanie Min, on 'The Bike Shed'. I highly recommend having a co-host because it adds value to your content and makes the recording process much more enjoyable.

00:11:12.000 This next question is for everyone: if someone were to ask you to describe the brand of your podcast, what would it be?

00:11:50.880 The brand of 'The Bike Shed' could be summed up as two people having a chat. It’s informal and conversational rather than following a traditional structure of interviews. This format aims to make it relatable and accessible to our audience.

00:12:10.740 I know Brittany’s podcast has an interview style, but I’ve heard those conversational episodes are the ones listeners enjoy the most.

00:12:37.620 Julie, what’s your approach to your podcast? Do you have a specific theme?

00:13:07.740 I tend to approach my podcast with themes based on subjects I’m confused about. By inviting knowledgeable guests, I can learn while also providing educational content for our audience. For instance, I recently invited a co-host to help explain the complexities of layoffs. It may seem selfish, but that’s the underlying motivation.

00:13:40.740 I think it’s important to note that if we only help one person with our episode, it’s worth it. In this case, that one person could be me!

00:14:12.360 So, Julie, would you agree that our community has room for more podcasts?

00:14:40.740 Absolutely! There’s always room for more content because there’s a wealth of knowledge and experience to be shared. My nervousness is only temporary, and it shouldn't prevent anyone from speaking up.

00:15:10.680 Joël, how do you handle technical topics on 'The Bike Shed' in an audio format?

00:15:56.220 It can be quite challenging, as coding is visual and textual. However, knowing your audience is key. Understanding their perspective and crafting the message for energetic engagement is crucial. We also ensure we communicate our points effectively.

00:16:24.660 Have you considered providing visual aids or prerequisites such as show notes before episodes?

00:16:49.740 I have thought about doing something creative with show notes. An idea I have is to share them as homework before an episode, especially for visually complex topics like dependency graphs.

00:17:08.520 This would help listeners feel more engaged and prepare for the conversation! So, are dependency graphs now the core brand of 'The Bike Shed'?

00:17:35.400 Yes! Let’s agree on that, especially since they help illustrate our discussions.

00:17:48.740 Andy, could you discuss the responsibilities involved in hiring a junior developer?

00:18:17.640 I’m currently hiring a junior developer through a boot-camp initiative. We decided that our team could accommodate a junior and that everyone should have a chance to succeed in programming, regardless of their experience level.

00:18:37.620 Our goal is to make this a fully paid position for one year, after which the junior developer will be well-equipped for opportunities.

00:19:01.680 We had 30 to 40 applicants primarily from boot camps in London, where I made an effort to go and talk about Ruby, distinguishing myself as a friendly and approachable candidate.

00:19:31.920 I encourage everyone to engage with their local boot camp communities and represent us positively.

00:19:45.060 Now, moving on to some listener questions! Our first question from Mina Slater is directed at Drew. How have you handled recording mishaps when planned episodes don't go well?

00:20:16.920 That seems to happen with every episode! I rely on my editor for assistance. I once had an episode where the audio quality was poor due to Zoom crashing. I reached out to my guest to see if we could redo it.

00:20:50.040 Most people are willing to re-record, especially when it’s a minor issue, and being honest about it can lead to great solutions.

00:21:02.820 Julie, can you share an episode recovery story from your podcast?

00:22:04.620 We’ve had episodes where feedback suggested that I wasn't participating enough. For instance, during an episode on Imposter Syndrome, I realized I was speaking only 5% of the time! I proposed re-recording it, focusing on making it a better conversation.

00:22:40.560 Andrew was very receptive to my suggestion, and we ended up with a well-rounded discussion.

00:23:10.740 So, where are you getting your feedback from?

00:23:50.640 I often reach out to our listeners via social media for their feedback. One time, I posted a Twitter request for feedback, and while most of the responses were positive, I did receive one direct message with constructive criticism.

00:24:42.780 I appreciate those insights because having someone point out areas for improvement is crucial. Andrew retweeted my post, encouraging users to be forthcoming with their feedback.

00:25:16.260 Before I had an editor, I did all the editing myself, and I learned many valuable lessons along the way.

00:25:55.920 One memorable experience involved a guest who was so nervous that we had to record their episode multiple times! Eventually, I suggested we practice while recording, and it turned out to be a great session!

00:26:24.420 I also had guests face unexpected distractions during recording, like emergency sirens or technical issues, but that's part of our podcasting experience.

00:26:53.520 So, as we wrap things up—how did you all find this experience at RubyConf Mini?

00:27:31.800 It's been exceptionally rewarding! I’m glad I got to help organize the panel, and I’m grateful to be a part of this community. Being in a space where we can learn from one another is invaluable.

00:28:10.440 So I'm excited for each of your upcoming talks as well!

00:28:25.200 Thank you, everyone! I appreciate the audience for their participation. It’s wonderful to know that we have support and that there are listeners out there engaging with our work.

00:28:43.800 I would like to close with a quote from Barbara Tannenbaum's keynote: 'We need your voices. We need people who care.' Thank you all!

RubyConf 2022 Mini