<?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: Ruth Evans</title>
    <description>The latest articles on DEV Community by Ruth Evans (@ruvans).</description>
    <link>https://dev.to/ruvans</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%2F88953%2F44f31233-a582-4534-bf8d-de02aae3853f.jpg</url>
      <title>DEV Community: Ruth Evans</title>
      <link>https://dev.to/ruvans</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ruvans"/>
    <language>en</language>
    <item>
      <title>How to code review in a start up?</title>
      <dc:creator>Ruth Evans</dc:creator>
      <pubDate>Tue, 02 Jul 2019 09:19:59 +0000</pubDate>
      <link>https://dev.to/ruvans/how-to-code-review-in-a-start-up-57pb</link>
      <guid>https://dev.to/ruvans/how-to-code-review-in-a-start-up-57pb</guid>
      <description>&lt;p&gt;I work in a small team of 5 developers and we've decided that we need to start doing code reviews which we definitely should have been doing already.&lt;br&gt;
I have experience for doing code reviews in my previous job for a large company were we could afford to spend the time and people on such tasks which is not the case here. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does anyone have any words of wisdom for code reviewing in small teams?&lt;/li&gt;
&lt;li&gt;How do you make time to review code?&lt;/li&gt;
&lt;li&gt;What do you do if there isn't a reviewer available who can understand that code or programming language?&lt;/li&gt;
&lt;li&gt;How do you resolve disputes when the reviewers and the authors are the same technical level?&lt;/li&gt;
&lt;/ul&gt;

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