Every time I answer a question more than once I look at it as an opportunity to write a blog. Unfortunately, in this extended March 2020 we continu...
For further actions, you may consider blocking this person and/or reporting abuse
Great post! I started in DevRel ~ 1.5 years ago. This post is very accurate, especially around sharing community feedback!
Like you mentioned, I have noticed some "Developer Experience" teams (often in the enterprise) focus on supporting their internal dev teams instead of the outside world.
A lot of the activities are similar (demos, office hours, gather feedback) but focused on an internal community instead of an external. Do you find yourself doing both in your role?
Yes! How I usually try to frame things for myself and my team currently is that anything we do internally we should approach with the idea we will take it external in some capacity.
Sometimes the internal enablement piece is a critical component of "winning" priority or helping the company understand the business reason or value.
That's really helpful!
Hey, I really like how you went full-send with this post. Currently, I am focusing on the usual full-stack engineering but, I feel I can provide value as an advocate (not particularly a devrel) somewhere in the future, mainly because it appeals to me and my communication skills are reasonable considering my background. Although, I currently lack professional experience with teams/organisations. You've broadened my view , in one post. Very thankful for this.
Full-send is pretty much 100% aligned to my personal brand. Thanks for your comment!
This is great. Adding to your list! DevEx should also include designing and battle-proofing workflows, and striving for creating a unified experience, that is, standardizing and making it easy to do the right/secure thing
Hey, how would you convince the management of a company that is quite new to development to create this position and allocate budget to it?
Big ask! Is this for internal or external?
Either way I would start by presenting a data-backed case.
Would be for internal
You can use what I mentioned above along with sprinkling in projects with the current dev team, but be super careful with scoping - "we can do this with x time and x people, but if we had y time and y people we could do this much more".
Hello from Austin
👋 What's up! Stay warm this week!
I was just having a conversation about this exact topic and specifically, the differences between developer experience and developer relations! Now I can link this blog instead :) Haha. Great post!
I would have rambled less but I hope it helps!
Hi amara! Would like to connect with you about your experience in DX!
Would you be open to a quick 20 min chat next week?