Behind the Mic: Adam Gordon Bell on Communication with Software Misadventures Podcast
CoRecursive: Coding Stories
Deep Dive
Why did Adam Gordon-Bell shift his career focus from being a software developer to communication and developer relations?
Adam realized that the people he admired, like Joel Spolsky, were not just great engineers but also great communicators. He understood that their impact came from their ability to explain and share knowledge, which led him to value communication more than just technical expertise. This realization shifted his career towards developer relations, where he could combine his technical skills with storytelling and communication.
What was Adam's first realization about the importance of communication in his career?
Adam's first inkling about the importance of communication came when he transitioned to a remote job and missed the informal knowledge-sharing that happened in the cafeteria at his previous workplace, Opertel. He noticed that much of the problem-solving knowledge was transferred through casual conversations, which he no longer had access to in a remote setting.
How did Adam get started in podcasting?
Adam got into podcasting after reaching out to Jeff from Software Engineering Daily, who needed help with interviews. Jeff suggested Adam find people to interview and send him the recordings. This led Adam to start his own podcast, Code Recursive, after Jeff stopped accepting external interviews and Adam had already booked several guests.
What is Adam's approach to storytelling in his podcast?
Adam focuses on finding stories where the protagonist has an objective and faces obstacles. He leans into the actual experiences of his guests, rather than just technical explanations. He believes that storytelling is about making everyday experiences compelling and relatable, even if they are not extraordinary.
What challenges did Adam face when starting his podcast?
The hardest part for Adam in the early days of starting his podcast was reaching out to potential guests and dealing with the fear of rejection. He also struggled with the editing process, which he found time-consuming but eventually embraced as a creative part of producing the podcast.
How does Adam prepare for podcast interviews?
Adam conducts pre-interviews with potential guests to understand their stories and ensure they are a good fit for the podcast. He uses a checklist to guide the conversation and focuses on finding moments where the guest had an objective and faced obstacles. He also allows the direction of the interview to change if something more interesting comes up during the conversation.
What role does music play in Adam's podcast editing process?
Adam uses music to enhance the storytelling in his podcast. He learned from NPR-style classes to use music to create momentum and emphasize key moments in the episode. He enjoys the process of adding music, even though it can be time-consuming, as it adds an emotional layer to the storytelling.
What is Adam's current goal with his podcast?
Adam's current goal is to make everyday experiences interesting and compelling through storytelling. He wants to explore how people's daily struggles and small victories can be turned into engaging stories that others can learn from, even if they are not extraordinary or dramatic.
How did Adam transition into developer relations?
Adam transitioned into developer relations after someone reached out to him about a role that involved communicating with developers. He initially struggled to find success but learned from Mitch Weiner, a founder of DigitalOcean, that the key was to understand developers' problems and provide solutions. This approach helped him grow in the role and focus on educating developers rather than just promoting products.
What does Adam believe is the most important skill in developer relations?
Adam believes that understanding developers' problems and providing solutions is the most important skill in developer relations. He emphasizes the importance of writing tutorials and educational content that helps developers solve their issues, rather than just promoting products. This approach builds trust and awareness of the product organically.
- The best engineers are often excellent communicators.
- Effective communication crystallizes complex ideas.
- Communication is more important than simply technical skills.
Shownotes Transcript