<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Surveys</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Surveys feed</description>
    <item>
      <title>Article: Curating Developer Experience: Practical Insights from Building a Platform Team</title>
      <link>https://www.infoq.com/articles/platform-engineering-developer-experience/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Surveys</link>
      <description>&lt;img src="https://res.infoq.com/articles/platform-engineering-developer-experience/en/headerimage/Curating-Developer-Experience-header-1725956305853.jpg"/&gt;&lt;p&gt;As a platform engineer, how do you help your customers go quicker, which aspects of developer experience should you care about and what do you actually do to curate an experience for them? This article is about curating a developer experience, it shares experiences and learnings from implementing DevEx and ideas on what platform engineers can do for development teams that use platforms.&lt;/p&gt; &lt;i&gt;By Andy Burgin&lt;/i&gt;</description>
      <category>Platform Engineering</category>
      <category>Product Management</category>
      <category>QCon London 2024</category>
      <category>Surveys</category>
      <category>Developer Experience</category>
      <category>QCon Software Development Conference</category>
      <category>Roadmap</category>
      <category>Culture &amp; Methods</category>
      <category>article</category>
      <pubDate>Thu, 19 Sep 2024 10:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/platform-engineering-developer-experience/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Surveys</guid>
      <dc:creator>Andy Burgin</dc:creator>
      <dc:date>2024-09-19T10:00:00Z</dc:date>
      <dc:identifier>/articles/platform-engineering-developer-experience/en</dc:identifier>
    </item>
  </channel>
</rss>
