<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bear Douglas on Medium]]></title>
        <description><![CDATA[Stories by Bear Douglas on Medium]]></description>
        <link>https://medium.com/@beardigsit?source=rss-7f914607f11f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tVHGdv2zdI_evFJCNmXlBA.jpeg</url>
            <title>Stories by Bear Douglas on Medium</title>
            <link>https://medium.com/@beardigsit?source=rss-7f914607f11f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:47:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@beardigsit/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Toward carbon neutral Developer Relations]]></title>
            <link>https://medium.com/@beardigsit/toward-carbon-neutral-developer-relations-24f013babc7a?source=rss-7f914607f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/24f013babc7a</guid>
            <category><![CDATA[climate-change]]></category>
            <category><![CDATA[developer-relations]]></category>
            <dc:creator><![CDATA[Bear Douglas]]></dc:creator>
            <pubDate>Wed, 02 Oct 2019 20:41:55 GMT</pubDate>
            <atom:updated>2019-10-02T20:41:55.587Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*chzZzOgORRsg6dpmdzMRZw.jpeg" /></figure><p>The urgency of climate change demands that we evolve how we live and work. As the #GlobalClimateStrike continues, as children from around the world are <a href="https://www.nationalgeographic.com/environment/2019/06/kids-suing-governments-about-climate-growing-trend/">taking governments to court</a> for our failure to protect their futures, it’s clear that we have to make radical changes in the way we practice Developer Relations.</p><p>Matthew Revell has talked about the importance of <a href="https://devrel.net/strategy-and-metrics/sustainable-developer-relations-matthew-revell">sustainable developer relations</a>, calling on us to reject the tendency to</p><blockquote>dress[...] up Developer Relations as a lifestyle that means, effectively, burning Antarctic ice by flying across the world…</blockquote><p>There are plenty of things we can do and already do for our communities and for our teammates that don’t involve hopping on planes. In the year since Matthew challenged us to think about this more deeply, the urgency to take action has only increased. We can’t stop at <em>sustainable</em> Developer Relations – we have to get to <em>carbon neutral</em>.</p><p>My team at Slack has business goals in progress for 2019 and 2020, external commitments that require travel, and a global team that benefits from some amount of face time. I’m sure yours does, too. Eliminating travel may not be feasible in the short term, but there are significant changes that we can make to ensure we’re meeting our burden of responsibility to minimize harm to our ecosystem.</p><h4>Practical plans for a carbon-neutral 2020</h4><p>Travel and events don’t constitute the majority of our work. 45+ weeks a year, we’re at our respective home bases, writing docs, building our SDKs, and working with partners and customers on their integrations– in person if they’re local, over VC if they’re not.</p><p>But it’s those other weeks of travel that have <a href="https://iopscience.iop.org/article/10.1088/1748-9326/aa7541/meta">the biggest impact</a> on the environment (and, let’s not forget, on our bodies). So what can we do about those?</p><p>My team has implemented a few policies to help minimize these moving forward:</p><ul><li>All flights are offset by 200%. <a href="https://www.cooleffect.org/">CoolEffect</a> provides offsets at a rate of ~$8/metric ton. Your company can afford this.</li><li>We take fewer trips and stay longer in region when we do. Flying internationally once a year for two weeks instead of twice a year for a week each time is kinder to the planet and to yourself.</li><li>We aim to stay at hotels that are LEED certified or similar, bringing business to the organizations that make their buildings energy efficient (a major factor in overall greenhouse gas emission).</li><li>No more electronic giveaways at our events. A branded Raspberry Pi is cute, but it’s as likely as not to end up as e-waste.</li><li>All swag must be made from recyclable materials. This one is still in progress as we work with our swag vendors to source sustainable options. Delivery of those materials is also offset.</li><li>Support events like <a href="https://medium.com/@DevrelSummit/devrel-summit-2019-carbon-neutral-34f051459863">DevRelSummit that go carbon-neutral</a>.</li></ul><p>The plan for 2020 relies heavily on carbon offsets. It’s a “for now” solution, because we are locked in (or feel we are) to a certain amount of travel– but offsets aren’t as good as just not emitting in the first place. Systems change and the switch to new energy sources can take decades to implement; we can choose to fly less <em>today.</em></p><blockquote><em>As a thought experiment: what if we just didn’t fly at all in 2021? How much of what we think is “necessary” travel may not be?</em></blockquote><h4>Beyond offsetting flights</h4><p>Making these adjustments is somewhere in the mushy middle space between individual action and systemic change. We’re asking individuals to rethink and be aware of their own travel– but if all heavy business travelers behaved similarly, what could we achieve?</p><p>Flights create the heaviest environmental load, but other small adjustments add up. There’s lots of room to cut down on waste at events– build less elaborate sets, reduce food and service waste, pick destinations that are well-served by public transit.</p><p>Supporting regional, community-led events is critical for fostering the connections that you make in face-to-face interactions, while reducing the travel burden on our teams and our developer communities.</p><p>Let’s get creative about the ways we can show up for our communities without hopping on a plane. I’m excited for <a href="https://medium.com/@colmdoyle/ee83de4d93a5">Tiny Spec</a>, a collection of local events after our big developer conference, Spec, where community groups around the world will host events on the same day around the world, keeping us physically local but helping us to connect globally.</p><h4>Share what you’re up to</h4><p>Lots of companies are cleaning up their acts. <a href="https://blogs.microsoft.com/green/2013/09/10/microsofts-carbon-offset-strategy-making-a-difference-one-project-at-a-time/">Microsoft</a> has been setting a great example; <a href="https://stripe.com/blog/carbon-neutral-journey">Stripe</a>, <a href="https://blog.lyft.com/posts/lyft-commits-to-full-carbon-neutrality-and-100-renewable-energy">Lyft</a>, and plenty of other companies have been following suit. We still <a href="https://twitter.com/jessalyn/status/1179068904137777152">have more to do</a> as a discipline– let’s talk about what we have going and what changes we can make together!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24f013babc7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Defining a career path for Developer Relations]]></title>
            <link>https://medium.com/several-people-are-coding/defining-a-career-path-for-developer-relations-cf70257352dd?source=rss-7f914607f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf70257352dd</guid>
            <category><![CDATA[developer-relations]]></category>
            <dc:creator><![CDATA[Bear Douglas]]></dc:creator>
            <pubDate>Thu, 14 Mar 2019 15:01:00 GMT</pubDate>
            <atom:updated>2019-03-14T15:01:00.902Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EbE4qvknu4gRTLjaUqJhxQ.jpeg" /></figure><p>Developer Relations (DevRel) is an interdisciplinary role that sits in a border space between product, engineering, and marketing. The daily work looks <a href="https://www.leggetter.co.uk/2016/02/03/defining-developer-relations.html">very different from company to company</a>, and because DevRel is often rolled into other organizations like product or marketing, it may not have its own separate career path – a document that describes expectations for your work at varying levels of seniority.</p><p>In recent months, more and more DevRel managers and ICs (individual contributors, meaning you don’t manage people) have been talking about how to write job descriptions and define career paths for Developer Relations. Today I want to help move the conversation forward in a more transparent way by sharing the career path I use for Developer Relations at Slack.</p><h4>Writing the path for Slack</h4><p>Developer Relations at Slack is currently a 12-person-strong team, and at this size, we’re generalists by preference and by necessity. Everyone writes docs, everyone builds tools and sample code, everyone gathers and shares developer feedback, and everyone works on events. We also come from different backgrounds: people on our team have joined us from core engineering, from developer support, from non-engineering operations roles, and some have been doing DevRel their entire careers. For our whole team, we have a single path.</p><p>Even for us, this path is imprecise, designed to be a set of guidelines rather than a series of job descriptions. Not everyone’s role will be neatly outlined by the content of the path, and, in my opinion, that’s not the point.</p><p>A good career path is general enough that it doesn’t box you in to a set of predefined activities. It’s also specific enough that you’re being held to a fair and clear standard of performance, while being shown a way forward to growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*m8yfLjWRzh1KJlyewbc4XQ.jpeg" /><figcaption><a href="https://medium.com/u/c5ad851c7af5">Helen Zeng</a> is a fantastic speaker, but it’s only one part of the job</figcaption></figure><p>In the past, I’ve found paths that described day-to-day work gave people an overly-prescriptive map of what to do to get promoted rather than a holistic understanding of how the organization defines seniority. It’s the latter that helps people create their own route to growth and promotion, which ultimately serves them and the company better.</p><p>In one of the first career paths I wrote, I described activities for a mid-level DevRel that included “running community events, like meetups.” As the team grew, the person who had been running our meetups asked me whether they would “lose the checkbox” toward promotion if they handed that responsibility over to someone else. To me, it was obvious that I wouldn’t care if this person <a href="https://slackhq.com/things-i-wish-someone-had-told-me-about-working-inside-a-scaling-company">gave away their Legos</a>– that was the healthy and correct thing to do in a growing team. To them, it was not so clear, because I had wrongly framed the conversation around <em>activities</em> rather than <em>behaviors</em>.</p><blockquote>To me, it was obvious that I wouldn’t care if this person gave away their Legos– that was the healthy and correct thing to do in a growing team. To them, it was not so clear, because I had wrongly framed the conversation around <em>activities</em> rather than <em>behaviors</em>.</blockquote><p>By contrast, I discussed Slack’s current DevRel path with one of our summer interns who wanted to understand what a full-time role and long-term career on our team might look like. After reading our path, our intern was able to accurately infer the levels of the people on our team he worked with most closely.</p><p>I realize that might make some people uncomfortable– shouldn’t that be private information, or something only discussed between you and your manager? But this information isn’t exactly private. Levels are encoded in job titles, and expressed in daily behaviors. If someone you work with casually can figure out what level you’re at, it shouldn’t feel risky, like you’ve been exposed– it’s a sign that your team is on the same page about what levels <em>are</em>.</p><h4>Enough philosophy, show us the levels</h4><p>OK, OK. You can jump to <a href="https://docs.google.com/spreadsheets/d/e/2PACX-1vSo9gklZdcNQok5LPaBunbHks6roG-mdvWPxCi41VXDWH3q-zW0T4Iyi8SKZa_1rUV0RFp8b6CsTds2/pubhtml">reading the full path here</a>, or I’ve excerpted it below for ease of reading.</p><p>Here’s what our level description looks like for a new grad:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VtCzvOaiH4mY6jhA-COs2w.png" /></figure><p>And here’s what it looks like for someone with a few years’ experience:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mxpgstyKdblZh-X7ZEqgww.png" /></figure><p>We define senior like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zsGlTFvB2OCL7Xk2dMCc8A.png" /></figure><p>And staff like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f3nGxE4-Y_I8ra07r7EB7w.png" /></figure><p>You’ll notice that the levels have three components: technical quality, collaboration, and execution (h/t to Ross Harmes, Matt Schweitz, and Lauren Ficklin, who wrote the Slack Engineering path that I adapted the DevRel path from). It’s meant to encompass growth in skills, in scope of work, and systems thinking– contextualizing our daily work in the broader landscape of businesses and technology.</p><p>Growing in your DevRel career means honing technical skill; it means being a better internal advocate for your developer customers; it means working to level your team up with you; and it means that you are a trusted communicator on behalf of the company. If you’re a great external communicator but you can’t get anything shipped for developers because you have no credibility with the product team, you aren’t becoming more senior in the organization. The same is true if you’re technically brilliant, but you never mentor anyone around you.</p><blockquote>The document describes a path that starts and grows purely in DevRel. But the path in (and out) of DevRel is highly individual, because the role is so interdisciplinary in nature.</blockquote><p>You may stay in DevRel for years, or spend some time here as a transition between engineering, marketing, product, sales engineering, business operations, user research, or data science (that’s a run-on on purpose– great DevRellians can come from anywhere).</p><p>Perhaps more than in other disciplines with traditional, linear career progressions, it’s important to distinguish between growth within the role and the organization, and growth in the broader context of a person’s career. Many people come to DevRel because they want to hone their technical presentation skills, or they want more exposure to customer developers. People who spend time in DevRel to better understand developer customers as part of a path to product or developer product marketing may care less about growing technically. For others, a role in DevRel may be the first time they’re responsible for production code.</p><p>Because people may come in with skill sets at different levels, and because it’s relatively rarer to spend your entire career in DevRel, it’s even more important to treat career paths as the jumping off point for conversations with your manager. Expectations for the role and a plan for growth should be individualized and made concrete in 1:1s.</p><p>Ultimately, the point of a career path is to help make sure that both you and your management chain see a path forward for you, as an individual contributor or a manager. It’s a level set, not a checklist, and with any luck, us sharing this detail can help you kick off that transparent conversation.</p><p>Does this sound like how you’re interested in growing your career? <a href="https://slack.com/jobs">We’re hiring</a>. Watch this space, and in the meantime, you can find me on Twitter at @beardigsit.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf70257352dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/several-people-are-coding/defining-a-career-path-for-developer-relations-cf70257352dd">Defining a career path for Developer Relations</a> was originally published in <a href="https://medium.com/several-people-are-coding">Several People Are Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Slack Platform Primer]]></title>
            <link>https://medium.com/slack-developer-blog/a-slack-platform-primer-57034d7bcf13?source=rss-7f914607f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/57034d7bcf13</guid>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Bear Douglas]]></dc:creator>
            <pubDate>Thu, 26 Jul 2018 20:07:53 GMT</pubDate>
            <atom:updated>2018-09-11T21:50:09.330Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Extending a warm welcome to Hipchat and Stride developers</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dw13Uvmg48qA9awHZ0ClSg.png" /></figure><p>Today, we’ve announced <a href="https://slackhq.com/atlassian-and-slack-partnership">an exciting new partnership with Atlassian</a> to deepen our existing integrations and provide our joint community of users better ways to collaborate at work.</p><p>To developers whose teams will be moving from Hipchat or Stride to Slack, we say a warm welcome! We know that you’ve put in work to integrate the tools you use daily using the Hipchat and Stride APIs, and we’re here to help as you think about migrating those integrations to Slack.</p><p>We’ve put together this primer to help you find the resources you need right away; those of you who have been developing with Slack’s APIs for a while may still find it useful as a map of our tools and developer content.</p><h3>Where do I get started?</h3><ul><li>We recommend that developers create a Slack workspace that’s separate from their production team to test their apps. You can <a href="http://slack.com/">create a free workspace</a> for that.</li><li>Check out our <a href="https://medium.com/slack-developer-blog/getting-started-with-slacks-apis-f930c73fc889">cheat sheet</a> for choosing the APIs you need for your top use cases.</li><li>We have <a href="http://api.slack.com/best-practices/blueprints">blueprints</a>– template apps– for some of the most common integrations. Cut straight to the chase by cloning one, or use it as a jumping-off point for something more complex.</li><li>Dive deeper into our APIs with our documentation on <a href="https://api.slack.com/">api.slack.com</a>.</li><li>If you’re writing an app for our App Directory, you can <a href="https://api.slack.com/tutorials/submitting-apps-to-the-directory">review our process</a> and recommendations for submitting.</li><li>Stay on top of updates, improvements, and new features by subscribing to our <a href="https://api.slack.com/changelog">changelog</a>, following <a href="http://twitter.com/slackapi">@SlackAPI</a> on Twitter, and reading our <a href="https://medium.com/slack-developer-blog">Platform blog</a>. For longer-term perspective on where we’re headed, you can also check out our <a href="https://trello.com/b/ZnTQyumQ/slack-platform-roadmap-for-developers">Platform Roadmap</a> on Trello.</li></ul><h3>What tools can I use?</h3><p>Our suite of developer tools is <a href="http://github.com/slackapi/">available on GitHub</a>, under @SlackAPI. That’s where you’ll find all our sample code, as well as our first-party SDKs.</p><ul><li>Slack provides <strong>SDKs</strong> for <a href="https://github.com/slackapi/python-slackclient">Python</a> and <a href="https://github.com/slackapi/node-slack-sdk">Node</a>, as well as a <a href="https://github.com/slackapi/hubot-slack">Hubot adapter</a>.</li><li><a href="https://github.com/slackapi/steno"><strong>Steno</strong></a> helps you record and replay calls to our API so you can write test cases for your integration.</li><li>Apps in Slack can send rich information in their messages using <a href="https://api.slack.com/docs/message-attachments">attachments</a>. Draft and craft them using our <a href="https://api.slack.com/docs/messages/builder"><strong>message builder</strong></a>.</li><li>Don’t see what you need? Check out the <a href="https://api.slack.com/tools">full list of developer tools</a>.</li></ul><h3>What if I want help from a human?</h3><ul><li>Our <strong>developer support</strong> team is here to help; you can contact us at <a href="/service/mailto:feedback@slack.com">feedback@slack.com</a></li><li><strong>Meet the community live</strong> at a <a href="https://www.meetup.com/pro/slackdevs/">Slack Platform Community Meetup</a> near you. If you don’t see one listed in your city, you can <a href="https://bit.ly/2Qameys">apply to host one</a>– we’ll reach out to help you get started!</li><li>Join us at Atlassian’s annual developer conference, <a href="https://www.atlassian.com/atlascamp">Atlas Camp</a>, to connect with the Slack and Atlassian teams. Use the code SLACK50EURO for €50 off your ticket!</li></ul><p><em>We’re looking forward to getting to know you! Drop us a line at feedback@slack.com, or reach out </em><a href="https://twitter.com/slackapi"><em>over Twitter</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57034d7bcf13" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slack-developer-blog/a-slack-platform-primer-57034d7bcf13">A Slack Platform Primer</a> was originally published in <a href="https://medium.com/slack-developer-blog">Slack Platform Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>