<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Logan Thomas</title>
    <description>The latest articles on DEV Community by Logan Thomas (@loganthomas).</description>
    <link>https://dev.to/loganthomas</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F26015%2F8ec3c0ca-4d0b-46b1-af94-020c45c9805b.jpeg</url>
      <title>DEV Community: Logan Thomas</title>
      <link>https://dev.to/loganthomas</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/loganthomas"/>
    <language>en</language>
    <item>
      <title>How do you perform Code Reviews?</title>
      <dc:creator>Logan Thomas</dc:creator>
      <pubDate>Thu, 23 May 2019 17:13:45 +0000</pubDate>
      <link>https://dev.to/loganthomas/how-do-you-perform-code-reviews-2hbc</link>
      <guid>https://dev.to/loganthomas/how-do-you-perform-code-reviews-2hbc</guid>
      <description>&lt;h2&gt;
  
  
  Question 1
&lt;/h2&gt;

&lt;p&gt;Within a large organization, I've heard that it's a best practice to limit code reviews to just a few developers that are actively working on a code base. What is your process for conducting code reviews in this setting?&lt;/p&gt;

&lt;h2&gt;
  
  
  Question 2
&lt;/h2&gt;

&lt;p&gt;What about getting a fresh set of eyes on the code base? Do you actively try to assign reviews to those who aren't involved in the day-to-day development of the code base (or even unfamiliar altogether with the code base)?&lt;/p&gt;

&lt;p&gt;Would love to hear your thoughts on the above!&lt;/p&gt;

</description>
      <category>discuss</category>
    </item>
  </channel>
</rss>
