What Is Developer Relations?  ## Metadata - Author: [[Justin Warren]] - Full Title: What Is Developer Relations? - Category: #articles - Document Note: --- tags: [DevRel, OpenSourceAdvocacy, CommunityManagement] Author: Justin Warren Source: Forbes Reference: [What is Developer Relations?](https://www.forbes.com/sites/justinwarren/2019/08/14/what-is-developer-relations/) date created: 2024-09-13 14:30 --- # Title: What is Developer Relations? ## Table of Contents: 1. [📝 Summary](#-summary) 2. [📖 Main Content](#-main-content) 3. [🗒️ Notes](#-notes) 4. [🗣️ Paraphrase](#-paraphrase) 5. [📰 Newsletter](#-newsletter) 6. [✅ Action Items](#-action-items) 7. [🧪 Hypotheses](#-hypotheses) 8. [📊 Methodology](#-methodology) 9. [❓ Questions](#-questions) 10. [🔮 Future Research](#-future-research) 11. [💡 Implications](#-implications) 12. [🧠 Learning Styles Assessment](#-learning-styles-assessment) 13. [📊 Accessibility Assessment](#-accessibility-assessment) 14. [🌍 DEIB Assessment](#-deib-assessment) 15. [✅ Logical Validity](#-logical-validity) 16. [🔍 SEO Evaluation](#-seo-evaluation) 17. [🎯 Conclusion](#-conclusion) ## 📝 Summary: The article "What is Developer Relations?" by Justin Warren provides an overview of the DevRel (Developer Relations) role. It emphasizes how DevRel bridges engineering, marketing, and community management to connect companies with developers. The role is multi-faceted, involving tasks like creating open-source projects, writing content, and engaging with the developer community. Various experts in the field, such as Eddie Zaneski and Mary Thengvall, share insights into how DevRel can help organizations, but they also highlight the challenges, including burnout and misaligned expectations. ## 📖 Main Content: Developer Relations (DevRel) is often described as a hybrid role that combines aspects of marketing, community management, and technical advocacy. Eddie Zaneski from DigitalOcean describes DevRel as "marketing for developers," a sentiment that some professionals reject. The role revolves around three key elements: **Code**, **Content**, and **Community**. The execution of these can vary significantly across organizations. Mary Thengvall stresses the importance of DevRel acting as a bridge between companies and the developer community, representing both sides equally. She warns, however, that if other departments are functioning well, a dedicated DevRel team may not be necessary. Rebecca Fitzhugh highlights the feedback loop that DevRel fosters between customers and product development teams, ensuring that developer needs are incorporated into product roadmaps. However, the role's ambiguity across organizations often leads to burnout, especially when DevRel teams are under-resourced or lack strategic direction. ## 🗒️ Notes: - **Three Cs of DevRel**: Code, Content, and Community - **DevRel Challenges**: - Burnout due to unclear expectations - Misalignment between company goals and community needs - DevRel’s success hinges on empathy and understanding of developer experiences - **Experts’ Take**: - Eddie Zaneski: Emphasizes DevRel as "marketing for developers." - Mary Thengvall: Stresses the dual representation of company and community interests. - Rebecca Fitzhugh: Highlights feedback loops between customers and engineering. ## 🗣️ Paraphrase: 1. **Original**: "DevRel, in theory, is the intersection of three disciplines: engineering, marketing, and community management." **Paraphrase**: The DevRel role ideally merges elements of engineering, marketing, and community management into a cohesive function. 2. **Original**: "To the community I represent the company, to the company I represent the community, and I must have both of their interests in mind at all times." **Paraphrase**: As a DevRel professional, it's essential to advocate for both the company and the community, keeping both perspectives in balance. ## 📰 Newsletter: In this issue, we're diving into **Developer Relations (DevRel)**, an evolving role bridging developers and enterprises. DevRel focuses on **code, content, and community** to ensure that products are built with developers' needs in mind. Leaders like **Mary Thengvall** and **Eddie Zaneski** weigh in on the importance of balancing corporate goals with community engagement. Whether you're creating content or building tools for developers, DevRel plays a pivotal role in shaping the future of open-source software. For more insights, check out the full article by **Justin Warren** at Forbes [here](https://www.forbes.com/sites/justinwarren/2019/08/14/what-is-developer-relations/). ## ✅ Action Items: - **Alignment with my role**: - Advocacy for **open-source contributors** fits naturally with DevRel’s focus on community engagement. - Emphasizing **education** aligns with the content creation pillar, through tutorials, blogs, and talks. - DevRel’s balance of company and community goals mirrors my advocacy for **transparency** and **sustainability** in open-source projects. - Insights from the article can guide efforts to build stronger relationships between **developers** and **product teams**. ## 🧪 Hypotheses: - Organizations with better integration of marketing and engineering may have less need for a dedicated DevRel team. - Empathetic leadership is crucial for preventing DevRel burnout. ## 📊 Methodology: - Surveys of DevRel professionals to assess the impact of empathy in leadership. - Case studies of organizations with and without DevRel teams to evaluate performance differences. ## ❓ Questions: - How can companies measure the success of a DevRel team? - What specific traits are most valuable in a DevRel professional? ## 🔮 Future Research: - The long-term impact of DevRel on developer retention and community growth. - Comparisons between DevRel strategies in open-source vs. closed-source companies. ## 💡 Implications: Effective DevRel could lead to more engaged developer communities and improved product feedback, ultimately contributing to more innovative and developer-friendly software solutions. ## 🧠 Learning Styles Assessment: 1. **Visual**: Limited—more diagrams or code snippets could enhance understanding. 2. **Aural**: No auditory options—could benefit from a podcast or audio format. 3. **Verbal**: Strong—well-written with clear language and examples. 4. **Physical**: Lacking actionable tasks—suggest including a hands-on activity. 5. **Logical**: Present—concepts are broken down logically, but more data could be included. 6. **Social**: Engages with the idea of community building. 7. **Solitary**: Could benefit from reflection prompts for personal application. 8. **Naturalistic**: Not applicable. ## 📊 Accessibility Assessment: - **Alt-text**: Ensure all images (if any) have alt text. - **Keyboard Navigation**: Check for proper focusable elements. - **Contrast**: Maintain readability with good contrast. - **Responsive Text**: Ensure text is scalable for better readability. ## 🌍 DEIB Assessment: - **Cultural Relevance**: Consider including more global examples of DevRel. - **Inclusive Language**: Generally neutral but could explicitly focus on underrepresented groups. - **Neurodiversity**: Breaking up long sections would improve readability for neurodiverse readers. ## ✅ Logical Validity: - **Sound Deductive Reasoning**: Thengvall's argument about balancing company and community interests is logically sound and strengthens the case for effective DevRel. - **Fallacies**: The claim that DevRel is "just marketing for developers" could be seen as an oversimplification, risking a **hasty generalization**. ## 🔍 SEO Evaluation: - **Keywords**: Strong use of "DevRel," "developer relations," and "community management." - **Meta Description**: Needs improvement—should clearly summarize the role and use keywords. - **Internal/External Links**: Lacks internal links but includes relevant external references. ## 🎯 Conclusion: The article effectively outlines the role of Developer Relations and its importance within organizations that rely on developer communities. It stresses the need for empathy and strategic alignment to avoid burnout and maximize impact. - Document Tags: [[devrel]] - Summary: Developer Relations, or DevRel, is a new job role in the cloud and enterprise industry that can be described as "marketing for developers." It involves three pillars: code, content, and community. However, the implementation of DevRel can vary widely across organizations, with different expectations and responsibilities. DevRel is about managing the relationship between the company and the developer community, representing both parties' interests. It can be valuable for organizations that target developers as an influential group, as it can help build rapport, gain insights, and make products sticky. However, setting up a DevRel team should be carefully considered and supported with a clear strategy and the right hires. - URL: https://www.forbes.com/sites/justinwarren/2019/08/14/what-is-developer-relations/ There's a hot new job role in cloud and enterprise vendors called Developer Relations, or DevRel for short, but what is it about? "I always call it marketing for developers," says Eddie Zaneski, Manager, Developer Relations at DigitalOcean. "There's definitely a large group of people that will hate that I say that. But at the end of the day, that's what DevRel is." "I like to describe the role as having three pillars," he says. "Three Cs: code, content, and community. Code is maybe open source projects, or quick starts examples. Content is blog posts, tutorials, talks, that kind of stuff. And then community is working with people in person or online, maybe Twitter or Stack Overflow." Matthew Broberg, Advocate and Editor at *opensource.com* says that in practice the implementation of DevRel has been far from consistent. "DevRel, in theory, is the intersection of three disciplines: engineering, marketing, and community management," he says. "In practice, DevRel applies to a wildly popular set of job titles with wildly different expectations across different organizations." "On a good day, DevRel fills one or more gaps in a company to connect them with technical consumers of their projects and products," Broberg says. "On a bad day, DevRel is a term used to hire people with large Twitter followings and ask them to do too much all at once until they inevitably hatequit or burnout or both." Mary Thengvall, founder of Persea Consulting and author of *The Business Value of Developer Relations,* says DevRel is really about managing the relationship between groups. "There's a phrase that I always go back to," she says, "To the community I represent the company, to the company I represent the community, and I must have both of their interests in mind at all times." Rebecca Fitzhugh, Principal Technologist at Rubrik agrees. "While there is certainly a marketing component when representing the company to the customer and community, it's equally about representing the customer to the company," she says. "Our DevRel team brings feedback from our customers to the product and engineering team in order to drive a better developer experience against our product's APIs." Organizations looking to create a developer relations team should carefully if such a team is really necessary. "If product is talking to marketing, who is talking to engineering who's talking to sales, and everyone's working together, you don't necessarily need a developer relations team," Thengvall says. "But there are so many companies these days that are Business to Developer that just don't understand those concepts." In many cases, the presence of a developer relations team indicates that the marketing function is broken. Using developer relations to glue back together the shattered fragments of an integrated marketing approach is likely to do more harm than good. If developers are the customers for your company's products, you just want some good ol' standard marketing, not developer relations. But for those organizations for whom developers are an influential group that aren't necessarily the main purchasers of the product, a developer relations team could be just as valuable as an analyst relations team, and for similar reasons. Building rapport with this group can put your products on the inside track for purchase, bypassing many of the complex hurdles of enterprise sales. Developers can also be a key source of insight about how your product actually gets used inside customers. Getting baked into the internal code pipeline can make a product sticky and hard for competitors to dislodge. "If you are spinning up a DevRel team, there's a good chance that you already have a deep backlog of things to do," says Fitzhugh. "It's important when you provide a clear strategy with tangible milestones that can be measured. Otherwise, with so much to do, it's easy to get lost in activities that aren't as impactful for the customer or the product." Franziska Hauck, Community and DevRel Expert, suggests that the people you choose to hire plays a vital part in the success of setting up a developer relations team. "Only hire empathetic people," she says. "They should have a good understanding of what devs have to deal with every single day. They need to be communicators, mediators, and helpmeets." As with most things, understanding what you're trying to achieve is the key to success. Setting up a DevRel team just because everyone else has one is an easy way to waste a lot of money on something pointless, or even harmful. A half-hearted and poorly supported DevRel initiative that gets shut down within six months can damage relationships with an influential group and directly affect product sales. Getting it right, however, can help to get your offering to the top of the consideration pile. , What Is Developer Relations?, Justin Warren, 01hnxmgz2h4sacnd7j4ht20d3v.