Developer Relations Roundtable - Hot and Spicy Topics

[[3. Resources/Readwise/Full Document Contents/Articles/Developer Relations Roundtable - Hot and Spicy Topics|Full Document Contents]]
## Document Notes
---
tags: #DevRel #DeveloperRelations #CommunityBuilding
- #DevRel
- #CommunityBuilding
- #DeveloperAdvocacy
Author: [Various Contributors]
Source: [Roundtable Discussion]
Reference: [YouTube Live Discussion]
date created: 2024-09-13 14:30
---
# Title: Spicy DevRel Roundtable Discussion: Insights and Hot Takes
## Table of Contents:
- [[#π Summary:]]
- [[#π Main Content:]]
- [[#ποΈ Notes]]
- [[#π§ Learning Styles Assessment:]]
- [[#π Accessibility Assessment:]]
- [[#π References:]]
- [[#π£οΈ Paraphrase:]]
- [[#π° Newsletter:]]
- [[#β
Action Items:]]
- [[#π§ͺ Hypotheses:]]
- [[#π SEO Evaluation:]]
- [[#π― Conclusion:]]
## π Summary:
The roundtable focused on various aspects of DevRel, including what makes a successful DevRel professional, the boundaries between DevRel and marketing, common mistakes when building developer communities, and spicy takes on whether DevRel can be performed as a service. Key points discussed were the challenges of DevRel as a career, managing burnout, and the necessity of authenticity when advocating for developer products.
## π Main Content:
### ποΈ Notes
- **Defining DevRel**: Developer relations is much more than marketing; it requires building trust, providing support, and connecting with the community.
- **Role Variety**: DevRel professionals wear many hats, such as content creators, technical writers, and community managers.
- **Developer Communities**: Building and maintaining a strong, engaged developer community is crucial for product success.
- **Biggest Mistakes in DevRel**:
- **Overhyping**: Avoid overselling products or setting unrealistic expectations for early-stage software.
- **Ignoring Feedback**: Not addressing community feedback can be detrimental to both product development and community trust.
- **DevRel as a Service**: It can work in specific contexts, particularly for early-stage startups that need specific tasks like documentation or video creation without hiring a full-time team member.
- **Specialization**: Sometimes outsourcing specific tasks like documentation or video creation is better than trying to have a DevRel professional do everything.
- **Challenges in DevRel**:
- **Burnout**: Constantly managing multiple tasks, engaging communities, and traveling can lead to burnout.
- **Balancing Communication**: The line between healthy communication and spamming is thin, and navigating it is key to building trust.
### π§ Learning Styles Assessment:
1. **Visual Learners (Spatial)**:
- **Present**: The use of clear diagrams or illustrations could enhance communication.
- **Improve**: Add more visual aids like infographics to explain complex ideas.
2. **Aural Learners (Auditory-Musical)**:
- **Present**: The conversational format aids auditory learners.
- **Improve**: Provide audio recordings or podcasts for those who prefer listening.
3. **Verbal Learners (Linguistic)**:
- **Present**: Detailed explanations were given.
- **Improve**: Incorporate analogies to help verbal learners grasp concepts better.
4. **Physical Learners (Kinesthetic)**:
- **Improve**: Include interactive tasks or real-world examples to engage kinesthetic learners.
### π Accessibility Assessment:
- **Screen Reader Compatibility**: Ensure that all visuals have alt-text, and the content is structured for accessibility.
- **Keyboard Navigation**: Enable users to navigate using only a keyboard for accessibility.
- **Text Resizing**: Content should remain responsive to different text sizes, ensuring readability for all users.
## π References:
- Roundtable discussion participants: Sabrina, Daniel, Hka, Sue, Mary, Francesco
- YouTube Live Stream: [DevRel Roundtable Discussion](https://www.youtube.com/watch?v=hLLmnarKopU)
## π£οΈ Paraphrase:
- "People often misunderstand DevRel as purely marketing or sales, but it's about building authentic relationships with developers by understanding their needs and delivering value." β The importance of building trust in developer communities.
- "Burnout is a common challenge in DevRel because you're constantly balancing content creation, community engagement, and travel. It's important to manage your workload and take breaks." β Balancing DevRel responsibilities to avoid burnout.
## π° Newsletter:
**This Week in DevRel**
In our latest roundtable, we dive deep into the spicy side of DevRel! From the misconceptions about developer advocacy to handling product flaws with grace, we cover it all. Our panelists shared insights on managing burnout, building authentic community relationships, and even debated the idea of DevRel as a service. If you missed it, catch up on the key points, including why overhyping your product is a big no-no, and learn how to advocate with integrity. Ready for more DevRel wisdom? Check out the full discussion here!
## β
Action Items:
As a Dev Advocate at GoDaddy, the roundtable discussion aligns with my goals of improving transparency in the open-source community, engaging new contributors, and fostering sustainable funding. The insights into avoiding burnout and how to handle tricky community-building challenges resonate with my focus on balancing advocacy and education.
## π§ͺ Hypotheses:
1. Developer advocacy that focuses on transparency and honesty will lead to higher community trust and product adoption.
2. Companies that offer DevRel as a service may attract startups or small companies with limited resources but need to ensure long-term engagement for better outcomes.
### π SEO Evaluation:
1. **Keywords**: Focus on "DevRel", "Developer Advocacy", "Building Developer Communities", and "Burnout in DevRel".
2. **Meta Description**: "Discover the best practices in DevRel and learn how to avoid common mistakes in building a developer community."
3. **Title Tag**: Ensure the title tag includes "Spicy DevRel Roundtable" and "Key DevRel Insights".
4. **Content Length**: This article should be comprehensive and long enough (1,500+ words) to cover DevRel topics in depth.
5. **Alt Text**: All images should have descriptive alt text for accessibility.
## π― Conclusion:
The roundtable provided insightful discussions on the many aspects of DevRel. By focusing on authenticity, effective communication, and understanding community needs, companies can avoid common pitfalls. DevRel as a service might suit specific business cases, but it's essential to balance short-term goals with long-term community-building efforts. Finally, maintaining trust within developer communities is key to sustainable success in developer relations.
Short Summary for [Developer Relations Roundtable - Hot and spicy topics](https://www.youtube.com/watch?v=hLLmnarKopU) by [Merlin](https://merlin.foyer.work/)
YouTube Video Title: Developer Relations Roundtable - Meet the Influential Developer Advocates & Engineers at Pixeles.
[00:04](https://www.youtube.com/watch?v=hLLmnarKopU&t=4) Introduction of participants in Developer Relations Roundtable
[02:34](https://www.youtube.com/watch?v=hLLmnarKopU&t=154) Introductions of the developers in the roundtable discussion
[07:41](https://www.youtube.com/watch?v=hLLmnarKopU&t=461) Importance of developer adoption
[10:00](https://www.youtube.com/watch?v=hLLmnarKopU&t=600) Importance of creating a community for product adoption
[14:45](https://www.youtube.com/watch?v=hLLmnarKopU&t=885) Effective communication with leadership and engineering is crucial for developer adoption.
[17:21](https://www.youtube.com/watch?v=hLLmnarKopU&t=1041) Some developers avoid coding and pivot to other roles.
[22:29](https://www.youtube.com/watch?v=hLLmnarKopU&t=1349) Increased demand for developers due to technology investments
[24:51](https://www.youtube.com/watch?v=hLLmnarKopU&t=1491) Companies lack consensus on the role of developer relations.
[29:38](https://www.youtube.com/watch?v=hLLmnarKopU&t=1778) Developer Advocates are crucial for building relationships with developers.
[31:50](https://www.youtube.com/watch?v=hLLmnarKopU&t=1910) Developing products with user feedback and e
> [!note]+ Document Notes
> tags: [DevRel, DeveloperRelations, CommunityBuilding]
> - #DevRel
> - #CommunityBuilding
> - #DeveloperAdvocacy
> Author: [Various Contributors]
> Source: [Roundtable Discussion]
> Reference: [YouTube Live Discussion]
> date created: 2024-09-13 14:30
>
> # Title: Spicy DevRel Roundtable Discussion: Insights and Hot Takes
>
<!-- deep-read:sections start -->
## Table of Contents:
- [π Summary](#-summary)
- [π Main Content](#-main-content)
- [ποΈ Notes](#-notes)
- [π§ Learning Styles Assessment](#-learning-styles-assessment)
- [π Accessibility Assessment](#-accessibility-assessment)
- [π References](#-references)
- [π£οΈ Paraphrase](#-paraphrase)
- [π° Newsletter](#-newsletter)
- [β
Action Items](#-action-items)
- [π§ͺ Hypotheses](#-hypotheses)
- [π SEO Evaluation](#-seo-evaluation)
- [π― Conclusion](#-conclusion)
## π Summary:
The roundtable focused on various aspects of DevRel, including what makes a successful DevRel professional, the boundaries between DevRel and marketing, common mistakes when building developer communities, and spicy takes on whether DevRel can be performed as a service. Key points discussed were the challenges of DevRel as a career, managing burnout, and the necessity of authenticity when advocating for developer products.
## π Main Content:
### ποΈ Notes
- **Defining DevRel**: Developer relations is much more than marketing; it requires building trust, providing support, and connecting with the community.
- **Role Variety**: DevRel professionals wear many hats, such as content creators, technical writers, and community managers.
- **Developer Communities**: Building and maintaining a strong, engaged developer community is crucial for product success.
- **Biggest Mistakes in DevRel**:
- **Overhyping**: Avoid overselling products or setting unrealistic expectations for early-stage software.
- **Ignoring Feedback**: Not addressing community feedback can be detrimental to both product development and community trust.
- **DevRel as a Service**: It can work in specific contexts, particularly for early-stage startups that need specific tasks like documentation or video creation without hiring a full-time team member.
- **Specialization**: Sometimes outsourcing specific tasks like documentation or video creation is better than trying to have a DevRel professional do everything.
- **Challenges in DevRel**:
- **Burnout**: Constantly managing multiple tasks, engaging communities, and traveling can lead to burnout.
- **Balancing Communication**: The line between healthy communication and spamming is thin, and navigating it is key to building trust.
### π§ Learning Styles Assessment:
1. **Visual Learners (Spatial)**:
- **Present**: The use of clear diagrams or illustrations could enhance communication.
- **Improve**: Add more visual aids like infographics to explain complex ideas.
2. **Aural Learners (Auditory-Musical)**:
- **Present**: The conversational format aids auditory learners.
- **Improve**: Provide audio recordings or podcasts for those who prefer listening.
3. **Verbal Learners (Linguistic)**:
- **Present**: Detailed explanations were given.
- **Improve**: Incorporate analogies to help verbal learners grasp concepts better.
4. **Physical Learners (Kinesthetic)**:
- **Improve**: Include interactive tasks or real-world examples to engage kinesthetic learners.
### π Accessibility Assessment:
- **Screen Reader Compatibility**: Ensure that all visuals have alt-text, and the content is structured for accessibility.
- **Keyboard Navigation**: Enable users to navigate using only a keyboard for accessibility.
- **Text Resizing**: Content should remain responsive to different text sizes, ensuring readability for all users.
## π References:
- Roundtable discussion participants: Sabrina, Daniel, Hka, Sue, Mary, Francesco
- YouTube Live Stream: [DevRel Roundtable Discussion](https://www.youtube.com/watch?v=hLLmnarKopU)
## π£οΈ Paraphrase:
- "People often misunderstand DevRel as purely marketing or sales, but it's about building authentic relationships with developers by understanding their needs and delivering value." β The importance of building trust in developer communities.
- "Burnout is a common challenge in DevRel because you're constantly balancing content creation, community engagement, and travel. It's important to manage your workload and take breaks." β Balancing DevRel responsibilities to avoid burnout.
## π° Newsletter:
**This Week in DevRel**
In our latest roundtable, we dive deep into the spicy side of DevRel! From the misconceptions about developer advocacy to handling product flaws with grace, we cover it all. Our panelists shared insights on managing burnout, building authentic community relationships, and even debated the idea of DevRel as a service. If you missed it, catch up on the key points, including why overhyping your product is a big no-no, and learn how to advocate with integrity. Ready for more DevRel wisdom? Check out the full discussion here!
## β
Action Items:
As a Dev Advocate at GoDaddy, the roundtable discussion aligns with my goals of improving transparency in the open-source community, engaging new contributors, and fostering sustainable funding. The insights into avoiding burnout and how to handle tricky community-building challenges resonate with my focus on balancing advocacy and education.
## π§ͺ Hypotheses:
1. Developer advocacy that focuses on transparency and honesty will lead to higher community trust and product adoption.
2. Companies that offer DevRel as a service may attract startups or small companies with limited resources but need to ensure long-term engagement for better outcomes.
### π SEO Evaluation:
1. **Keywords**: Focus on "DevRel", "Developer Advocacy", "Building Developer Communities", and "Burnout in DevRel".
2. **Meta Description**: "Discover the best practices in DevRel and learn how to avoid common mistakes in building a developer community."
3. **Title Tag**: Ensure the title tag includes "Spicy DevRel Roundtable" and "Key DevRel Insights".
4. **Content Length**: This article should be comprehensive and long enough (1,500+ words) to cover DevRel topics in depth.
5. **Alt Text**: All images should have descriptive alt text for accessibility.
## π― Conclusion:
The roundtable provided insightful discussions on the many aspects of DevRel. By focusing on authenticity, effective communication, and understanding community needs, companies can avoid common pitfalls. DevRel as a service might suit specific business cases, but it's essential to balance short-term goals with long-term community-building efforts. Finally, maintaining trust within developer communities is key to sustainable success in developer relations.
Short Summary for [Developer Relations Roundtable - Hot and spicy topics](https://www.youtube.com/watch?v=hLLmnarKopU) by [Merlin](https://merlin.foyer.work/)
YouTube Video Title: Developer Relations Roundtable - Meet the Influential Developer Advocates & Engineers at Pixeles.
[00:04](https://www.youtube.com/watch?v=hLLmnarKopU&t=4) Introduction of participants in Developer Relations Roundtable
[02:34](https://www.youtube.com/watch?v=hLLmnarKopU&t=154) Introductions of the developers in the roundtable discussion
[07:41](https://www.youtube.com/watch?v=hLLmnarKopU&t=461) Importance of developer adoption
[10:00](https://www.youtube.com/watch?v=hLLmnarKopU&t=600) Importance of creating a community for product adoption
[14:45](https://www.youtube.com/watch?v=hLLmnarKopU&t=885) Effective communication with leadership and engineering is crucial for developer adoption.
[17:21](https://www.youtube.com/watch?v=hLLmnarKopU&t=1041) Some developers avoid coding and pivot to other roles.
[22:29](https://www.youtube.com/watch?v=hLLmnarKopU&t=1349) Increased demand for developers due to technology investments
[24:51](https://www.youtube.com/watch?v=hLLmnarKopU&t=1491) Companies lack consensus on the role of developer relations.
[29:38](https://www.youtube.com/watch?v=hLLmnarKopU&t=1778) Developer Advocates are crucial for building relationships with developers.
[31:50](https://www.youtube.com/watch?v=hLLmnarKopU&t=1910) Developing products with user feedback and evolution
[36:56](https://www.youtube.com/watch?v=hLLmnarKopU&t=2216) Importance of finding your niche and being honest in developer relations
[38:51](https://www.youtube.com/watch?v=hLLmnarKopU&t=2331) Building trust with developers is key in developer relations.
[43:07](https://www.youtube.com/watch?v=hLLmnarKopU&t=2587) Transitioning from developer relations to coding and vice versa
[45:20](https://www.youtube.com/watch?v=hLLmnarKopU&t=2720) Managing burnout and switching activities
[50:15](https://www.youtube.com/watch?v=hLLmnarKopU&t=3015) Skills diversity leads to higher pay in developer relations roles.
[52:14](https://www.youtube.com/watch?v=hLLmnarKopU&t=3134) Communication is key for success and failure in a developer career
[57:10](https://www.youtube.com/watch?v=hLLmnarKopU&t=3430) Importance of transparency and feedback in software development
[58:56](https://www.youtube.com/watch?v=hLLmnarKopU&t=3536) Focus on showcasing how your product makes developers' lives faster
[1:03:28](https://www.youtube.com/watch?v=hLLmnarKopU&t=3808) Engage with communities without spamming
[1:05:48](https://www.youtube.com/watch?v=hLLmnarKopU&t=3948) Discussion on the complexities of the crypto community
[1:10:31](https://www.youtube.com/watch?v=hLLmnarKopU&t=4231) Hiring Devals for video creation depends on goals
[1:12:37](https://www.youtube.com/watch?v=hLLmnarKopU&t=4357) Discussing challenges faced by smaller companies
[1:17:12](https://www.youtube.com/watch?v=hLLmnarKopU&t=4632) Focus on value over metrics for successful developer career
[1:19:45](https://www.youtube.com/watch?v=hLLmnarKopU&t=4785) Developers don't need to be the best coders to succeed in developer relations
---------------------------------
Detailed Summary for [Developer Relations Roundtable - Hot and spicy topics](https://www.youtube.com/watch?v=hLLmnarKopU) by [Merlin](https://merlin.foyer.work/)
YouTube Video Title: Developer Relations Roundtable - Meet the Influential Developer Advocates & Engineers at Pixeles.
[00:04](https://www.youtube.com/watch?v=hLLmnarKopU&t=4) Introduction of participants in Developer Relations Roundtable
- Mary from Pixeles introduces herself as a design engineer new to live streaming
- Daniel, a developer advocate from the UK, shares his recent travel experience and meeting at World Congress
[02:34](https://www.youtube.com/watch?v=hLLmnarKopU&t=154) Introductions of the developers in the roundtable discussion
- Various developers from different backgrounds and experiences introduced themselves.
- The roundtable includes developers from Shopify, Neel, and front-end development backgrounds.
[07:41](https://www.youtube.com/watch?v=hLLmnarKopU&t=461) Importance of developer adoption
- Documentation and developer experience are key for product adoption.
- Developer evangelism plays a crucial role in promoting product adoption.
[10:00](https://www.youtube.com/watch?v=hLLmnarKopU&t=600) Importance of creating a community for product adoption
- Creating a community is crucial for product adoption as it drives usage and understanding
- It is essential to have guidance on when and how to create a community to avoid having a 'ghost town' with no engagement
[14:45](https://www.youtube.com/watch?v=hLLmnarKopU&t=885) Effective communication with leadership and engineering is crucial for developer adoption.
- Align job expectations with leadership and engineering to find common ground.
- Encourage flexibility and open communication to experiment, discuss results, and find the best approach for developer adoption.
[17:21](https://www.youtube.com/watch?v=hLLmnarKopU&t=1041) Some developers avoid coding and pivot to other roles.
- Developers reaching out for help at odd hours.
- Discussion about developers shifting away from coding.
[22:29](https://www.youtube.com/watch?v=hLLmnarKopU&t=1349) Increased demand for developers due to technology investments
- New investments in technology startups have led to a surge in demand for developers.
- The changing landscape in tech industry has created opportunities for developers in diverse roles.
[24:51](https://www.youtube.com/watch?v=hLLmnarKopU&t=1491) Companies lack consensus on the role of developer relations.
- The debate about whether developer advocacy is marketing or sales continues, with different companies seeing it differently.
- There is a need for a diverse team to handle developer product or tooling, including roles like developer advocate, demand generation, sales, community manager, and communications personnel.
[29:38](https://www.youtube.com/watch?v=hLLmnarKopU&t=1778) Developer Advocates are crucial for building relationships with developers.
- They focus on building feedback loops, communication, and community with developers.
- Early stage products for developers often require founders or engineering teams to handle developer relations work until the product gains traction.
[31:50](https://www.youtube.com/watch?v=hLLmnarKopU&t=1910) Developing products with user feedback and evolution
- Experimenting with product definition for two years, embracing evolution
- Importance of advocating for popular and needed technologies
[36:56](https://www.youtube.com/watch?v=hLLmnarKopU&t=2216) Importance of finding your niche and being honest in developer relations
- Finding your niche in terms of technologies and industries can shape your career path and help in making informed decisions.
- Being honest in developer relations is crucial to maintain credibility and reputation, avoiding misleading developers about products or services.
[38:51](https://www.youtube.com/watch?v=hLLmnarKopU&t=2331) Building trust with developers is key in developer relations.
- Developers can see through dishonesty and value genuine connections.
- Advocacy shouldn't feel forced; genuine love for the product is essential.
[43:07](https://www.youtube.com/watch?v=hLLmnarKopU&t=2587) Transitioning from developer relations to coding and vice versa
- Discussing the impact of working in developer relations on returning to coding professionally
- Exploring the challenges and potential burnout of transitioning from coding to developer relations
[45:20](https://www.youtube.com/watch?v=hLLmnarKopU&t=2720) Managing burnout and switching activities
- Taking a break can help alleviate stress and avoid burnout.
- Switching between coding and other activities can be an effective strategy for developers.
[50:15](https://www.youtube.com/watch?v=hLLmnarKopU&t=3015) Skills diversity leads to higher pay in developer relations roles.
- Companies value individuals with multiple skills by offering higher compensation.
- Developers with diverse skills in communication, content creation, and community engagement are in high demand.
[52:14](https://www.youtube.com/watch?v=hLLmnarKopU&t=3134) Communication is key for success and failure in a developer career
- Being communicative and clear is crucial for success
- Balancing communication skills is essential for career growth
[57:10](https://www.youtube.com/watch?v=hLLmnarKopU&t=3430) Importance of transparency and feedback in software development
- Transparency in acknowledging issues builds trust with the audience and helps in product improvement.
- Feedback and communication with developers from day one is crucial for product enhancement and roadmap clarity.
[58:56](https://www.youtube.com/watch?v=hLLmnarKopU&t=3536) Focus on showcasing how your product makes developers' lives faster
- Communicate trends without comparing to competitors, focus on speed and efficiency
- Prioritize great support and community feedback to build developer trust
[1:03:28](https://www.youtube.com/watch?v=hLLmnarKopU&t=3808) Engage with communities without spamming
- Spamming developers in communities may not be necessary to keep them engaged and provide valuable feedback.
- Some crypto communities can exhibit strange behaviors, mixing discussions on various topics like NFTs, Tesla, financial markets, and political views.
[1:05:48](https://www.youtube.com/watch?v=hLLmnarKopU&t=3948) Discussion on the complexities of the crypto community
- It is recognized that there are both positive and negative aspects within the crypto industry. There is a mix of professionalism and questionable practices.
- The reputation of those working seriously in crypto is sometimes undermined by others not taking it seriously, leading to frustrations.
[1:10:31](https://www.youtube.com/watch?v=hLLmnarKopU&t=4231) Hiring Devals for video creation depends on goals
- Consider multiple video creators for larger audience reach
- For long partnerships on specific topics, hiring a dedicated Deval may be beneficial
[1:12:37](https://www.youtube.com/watch?v=hLLmnarKopU&t=4357) Discussing challenges faced by smaller companies
- Smaller companies struggle with task delegation and company direction
- Limited resources lead to difficulties in hiring full-time personnel
[1:17:12](https://www.youtube.com/watch?v=hLLmnarKopU&t=4632) Focus on value over metrics for successful developer career
- Quality over quantity is crucial in developer relations for long-term success
- Creating valuable content like blogs can significantly impact a career in Dev
[1:19:45](https://www.youtube.com/watch?v=hLLmnarKopU&t=4785) Developers don't need to be the best coders to succeed in developer relations
- Developer relations roles are diverse and can accommodate different skill sets
- Success in developer relations depends on one's ability to engage and support the developer community
<!-- deep-read:sections end -->
## Highlights
- the
hyp overstressed folks do you know a person like has been in Devil then coding and then they came back to theil I don't I don't I think I don't know a single person with like this triple triple switch I know people who are who went back to coding but still not anyone maybe we need to wait couple more gear do you know anyone without even mentioning names like that after let's
say uh stop being the they they got another devil role I think I don't know anyone should be um should uh like take a cold vacation to to stay real good the uh but do you that long vacation that we were talking about earlier I me
I mean you as a I think you need to switch your activities like um I don't know like doing the stuff and so on and when you see that you close to burnout or something like that you can switch to coding uh codes as much as you need and then back to your deril St I think it's ideal ([View Highlight](https://read.readwise.io/read/01j7nvq2zhzps44vp7r8aesrf9))