<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer Experience Audit on Chris Reddington</title><link>https://chrisreddington.com/tags/developer-experience-audit/</link><description>Recent content in Developer Experience Audit on Chris Reddington</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sat, 14 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chrisreddington.com/tags/developer-experience-audit/index.xml" rel="self" type="application/rss+xml"/><item><title>Developer experience: prerequisite and product of DevRel</title><link>https://chrisreddington.com/blog/devrel-developer-experience/</link><pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate><guid>https://chrisreddington.com/blog/devrel-developer-experience/</guid><description>&lt;p&gt;I&amp;rsquo;ve written before about &lt;a href="https://chrisreddington.com/blog/devrel-value-creation/"&gt;how DevRel creates value and what that looks like in practice&lt;/a&gt;, and &lt;a href="https://chrisreddington.com/blog/devrel-value-co-creation-not-marketing/"&gt;why DevRel is better understood as value co-creation than as marketing&lt;/a&gt;. My second post described Developer Experience (DX) as the &amp;ldquo;value-in-use&amp;rdquo; dimension of value co-creation: the value a developer actually experiences when using the product. This post picks up from there and focuses on developer experience specifically: what it actually means, why it sits at the centre of DevRel strategy, and the nuance I think most writing on DevRel misses.&lt;/p&gt;</description></item></channel></rss>