There are some great questions popping up from the community this week! Take a few minutes to help out your DevRel colleagues.
Dev Rel Twitter - I need your help. I'm new to this field and I need to start working on my career development plan. What are some good goals for year one in this field?
Hey avocados! What internet plans do you use when you are traveling abroad (outside of EU and US)? Are you using any of those devices which "huge" coverage like Skyroam?
Writers, have you always liked writing?
If not, why didn't you, and how did you learn to like it?
What does it take to do social media well for #developer communities? #devrel
I couldn't agree more strongly with this assertion from David Spinks:
A lot of problems go away when you can connect community activity (attendees offline, active users online) to customer data (revenue & retention).
That means you need a CRM and your community software needs to connect to it.
Only 1/3 of community teams can currently do this.
This is a point I've been doubling down on with all of my clients. We need to document interactions with community members. It's not "gross" -- it's necessary for our teams to be successful. How else are we going to prove our value?
In addition, it's helpful for remembering where we met people, what their hobbies are, and who exactly lives in Chicago, programs in Python, and enjoys public speaking for when we need to recommend a community speaker to a meetup. We suddenly don't have to keep all of that information in our heads, which frees us up to focus on other tasks, and allows us to delegate the finding of said speakers to others on our team.
Bonus: When you leave your team (as most of us eventually do), you won't be leaving them in the lurch. Instead of you holding all of the community relationships in your head, they've been building relationships with those community members right alongside you and they have all of the history to back it up while you're moving on to your next big gig.