<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Devrel on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/devrel/</link><description>Recent content in Devrel on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 26 Sep 2024 11:55:28 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/devrel/index.xml" rel="self" type="application/rss+xml"/><item><title>Developer Relations as Terraforming: Cultivating Ecosystems for Success</title><link>https://javapro-en.svenruppert.com/developer-relations-as-terraforming-cultivating-ecosystems-for-success/</link><pubDate>Thu, 26 Sep 2024 11:55:28 +0000</pubDate><guid>https://javapro-en.svenruppert.com/developer-relations-as-terraforming-cultivating-ecosystems-for-success/</guid><description>&lt;p&gt;As a “DevRel” person, I’m disappointed in how often our efforts are misunderstood and marginalised. In this article, I want to take another slant on the what and why of “DevRel.”&lt;/p&gt;
&lt;p&gt;Developer Relations (DevRel) holds the same transformative potential as terraforming in science fiction. It&amp;rsquo;s cheesy, but it’s pretty accurate. Much like engineers striving to turn a hostile, barren planet into one that can sustain life, DevRel teams are tasked with creating an atmosphere where developers can thrive. Success in both cases isn’t immediate; it requires patience, deliberate planning, and constant care to cultivate a living ecosystem.&lt;/p&gt;</description></item><item><title>the Wild Frontier of Technology adoption</title><link>https://javapro-en.svenruppert.com/the-wild-frontier-of-technology-adoption/</link><pubDate>Tue, 13 Aug 2024 09:55:32 +0000</pubDate><guid>https://javapro-en.svenruppert.com/the-wild-frontier-of-technology-adoption/</guid><description>&lt;p&gt;Being out of work and looking for new opportunities means interviews. A common thread that comes up is arm waving. &amp;ldquo;There are 25 million developers out there, we want you to make them use our product/api/service&amp;rdquo;. Coupled with this idea is the expectation that if only they could get the offering in front of a developer if only that developer would try it, then all would be well and money would pour in.&lt;/p&gt;</description></item></channel></rss>