If you missed DevXcon this past week, chances are you didn't miss seeing the happenings on Twitter! If you've been frantically trying to catch up on the Twitter stream, I'll warn you -- there's a lot! But if you're looking for a distilled version, check out Dave Nugent's awesome summary.
I take notes by live-tweeting, which others have told me benefits them as well! For the first time, I created a Twitter moment based on these tweets. If a particular talk sounds interesting to you, click through on the tweet to find the rest of the talk in the thread. (Pro tip: If you don't like reading Twitter threads, there are a few workarounds.)
Here are a few of my favorite tweets from the conference:
Strategies for finding your position in DevRel:
- Help your company understand why it makes the product
- Be honest with users about why the product exists
- Help the company understand why meeting user needs advances their needs
- Keep your integrity 🙌
Things that don't work [in emails to developers]:
*Subject lines don't move the needle.
* Designs don't matter
* Sending dates and times don't matter.
* Don't worry about the hecklers. Only worry about your friends and people trusted in the community.
As someone who recently moved into "leadership" a motivation was an experience of being poorly lead elsewhere & the negative impact that had on me and the people I worked with. I wanted to prove that a collaborative and individual-empowering approach to #DevRel can work. Another big motivation was seeing DevRel teams come and go at far too many companies. I wanted to clearly demonstrate the value of DevRel within a company and the industry. I also prefer DevRel outside of the marketing function and wanted to demonstrate success in that. #DevXCon
More analysis came from The Community Roundtable survey this week, including this gem:;
While communities generate a multitude of value, this power to support and challenge individuals so they can learn and grow in emotionally safe spaces is the key reason to invest in strong communities.
We all know this principle to be true: "To write good documentation, you have to follow the most fundamental rule of writing: know your reader." However... what happens when your reader isn't making themselves known? We're all grateful for the lurkers (truth be told, we've all probably been lurkers at some point in time!) but when they're silent, how do you know whether you're creating documentation that's useful for them?
I'd Rather be Writing digs into this problem this week and gives us a few useful tips along the way.
Yet another development in the Facebook saga has some of us moving further and further away from the platform (or at least from supporting it financially). As Rachel Happe said earlier this week,
More reasons not to put your organization's community on Facebook... they get the data, ISPs get the data... but you don't get the data. They know just how valuable the data is... does your org?!?
Where do you fall on the Facebook spectrum? Hit reply and let me know.
Microsoft Acquires Github
This headline shouldn't be a surprise for anyone, but in case it is... surprise! Microsoft blogged about it, as did Github, both of which were incredibly upbeat articles (no surprise there either), but the response from the community was mixed to say the least.
There are too many blogposts, tweet threads, and news podcasts to list here, but this one from Anil Dash caught my eye. (Disclaimer: it is framed as a pitch for Glitch, but keep reading until the end...)
The bullet points toward the bottom of the article (search for "What about other tools?" if you want to skip straight there) raise good points about where Github (and other platforms) have missed the bar over the years. This point at the end of the article particularly hits home for me:
GitHub has radically changed coding in the last 10 years, and we should all celebrate this milestone for Microsoft and for the community. It’s a validation of an important idea: We don’t code alone.
We can all agree on that, regardless of where we fall of the Microsoft/Github spectrum. Thoughts & feelings? Hit reply and let me know.