<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - ?????????????? - アーティクル</title>
    <link>https://www.infoq.com/jp</link>
    <description>InfoQ ?????????????? アーティクル フィード</description>
    <item>
      <title>アーティクル: Netflixにおける開発体験のスケールアップと成長</title>
      <link>https://www.infoq.com/jp/articles/developer-experience-netflix/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/developer-experience-netflix/ja/headerimage/generatedHeaderImage-1658308092283.jpg"/&gt;&lt;p&gt;An optimal Developer Experience will depend a lot on the company the developer is working for. This article discusses why and when changes to developer needs will occur, how to get ahead of them, and how to adapt when these changes are necessary. I talk through some of the experiences myself and peers have had at Netflix, identifying some key learnings and examples we have gained over the years.&lt;/p&gt; &lt;i&gt;By Phillipa Avery&lt;/i&gt; &lt;i&gt; Translated by Tomoo Morikawa, Ayako Ueno&lt;/i&gt;</description>
      <category>??????????????</category>
      <category>Artifacts &amp; Tools</category>
      <category>カルチャー＆手法</category>
      <category>DevOps</category>
      <category>アーティクル</category>
      <pubDate>Mon, 12 Jun 2023 05:32:00 GMT</pubDate>
      <guid>https://www.infoq.com/jp/articles/developer-experience-netflix/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F-articles</guid>
      <dc:creator>Phillipa Avery</dc:creator>
      <dc:date>2023-06-12T05:32:00Z</dc:date>
      <dc:identifier>/articles/developer-experience-netflix/ja</dc:identifier>
    </item>
  </channel>
</rss>
