What does DevRel mean and how it important ?
A few days ago, I embarked on a new adventure that involves diving into the fascinating world of DevRel. One of the pillars of DevRel that fascinates me the most is sharing my knowledge with others, so I decided to share what I learned about DevRel on my blog. Today I'm going to share with you what I've learned about devrel in the first week of my DevRel adventure. I've titled it "What is DevRel?". Enjoy
Plan
Introduction
Definition
The different aspects of DevRel
Conclusion
Introduction
With technology's ability to solve problems from the least complex to the most complex, more and more people are embarking on the creation of innovative solutions with programming. Companies such as Microsoft, Google etc. are creating products or ecosystems to enable developers to create solutions. To ensure that their products can be adopted by multiple developers, these companies need someone who both understands the company's products and understands the developers too. This person is the DevRel (Developer relation).
Definition
DevRel stands for Developer relation. He or she is the bridge between developers who use an organization's product and the organization in question. He or she is the product evangelist and developer advocate. He or she ensures smooth communication between the developers and the organization, and is responsible for receiving feedback from the developers and helping them to understand the product. He or she is the ambassador.
The different aspects of DevRel
you'd have noticed that DevRel isn't a simple role, but a fascinating set of roles essential for growth, both for the developer and for the product:
Developer Advocacy and Developer evangelism
Developer Advocate: It's the person who is the voice of the developers, the loudspeaker of the developers. He or she is responsible for defending the developers' interests within the organization by clearly communicating the developers' needs. He or she is the developers' representative within the company.
Developer Evangelist: Like the developer advocate, the developer evangelist is the organization's spokesperson to the developer community. He or she is responsible for promoting the product and its widespread adoption by developers. He or she is the product's advocate. He or she clearly communicates all changes, improvements and advances to the product.
NB: sometimes the developer advocate and the developer evangelist are one and the same.
Community Management
Community Manager: He or she is responsible for keeping the community dynamic and lively. He or she takes large-scale initiatives to enable community members to have opportunities
Developer Education
Developer Educator: he or she is responsible for educating developers about the product by creating resources (blog, article, YouTube video etc.) to allow developers to quickly get to grips with the product and accelerate the development of their solutions
Developer Marketing
Developer Marketer: The developer marketer is responsible for advertising the product and thus enabling the adoption of the product by several developers
DevRel's responsibilities
A DevRel has several responsibilities which are all crucial:
Technical content: A DevRel is responsible for creating technical content to facilitate understanding of the product. This content can be (blog, article, youtube video, vimeo etc...)
Developer Experience: One of the key responsibilities of a DevRel is to ensure that developers have a better experience of the product.
Application development: Although the DevRel is not a software engineer, he or she can sometimes code too. DevRel doesn't mean you can't code. The DevRel may sometimes be called upon to add new features to the application, or help the engineering team with bug debugging, or write unit tests etc...
Community development: The DevRel is responsible for the growth of the community in terms of human resources, both quantitatively and qualitatively.
Conclusion
The DevRel (Developer Relationship) is very important in an organization for maintaining a win-win relationship between the organization and the developers. I will be delighted to learn from you regarding the devrel if you have any constructive comments, I would appreciate it. Thank you for reading, sharing. See you in the next blog