<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer Communities on Chris Reddington</title><link>https://chrisreddington.com/tags/developer-communities/</link><description>Recent content in Developer Communities on Chris Reddington</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Thu, 19 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chrisreddington.com/tags/developer-communities/index.xml" rel="self" type="application/rss+xml"/><item><title>Company context: the conditions that shape DevRel strategy</title><link>https://chrisreddington.com/blog/devrel-company-context-lifecycle/</link><pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate><guid>https://chrisreddington.com/blog/devrel-company-context-lifecycle/</guid><description>&lt;p&gt;I&amp;rsquo;ve seen DevRel teams borrow someone else&amp;rsquo;s playbook and assume it&amp;rsquo;ll work for them too.&lt;/p&gt;
&lt;p&gt;A team sees what a well-regarded DevRel organisation does, the community programs, the content formats, the event strategy, the metrics, and tries to replicate it. It doesn&amp;rsquo;t work as well. Sometimes it doesn&amp;rsquo;t work at all. The conclusion drawn is often something about execution quality or budget. Rarely is the conclusion about context.&lt;/p&gt;
&lt;p&gt;But context is often exactly the issue.&lt;/p&gt;</description></item></channel></rss>