<?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: Filisha</title>
    <description>The latest articles on DEV Community by Filisha (@filisha12).</description>
    <link>https://dev.to/filisha12</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%2F162138%2F24a0f1d6-7bf8-44c3-9059-270452ede900.jpg</url>
      <title>DEV Community: Filisha</title>
      <link>https://dev.to/filisha12</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/filisha12"/>
    <language>en</language>
    <item>
      <title>Is there a pattern to collaboration?</title>
      <dc:creator>Filisha</dc:creator>
      <pubDate>Fri, 20 Sep 2019 01:13:32 +0000</pubDate>
      <link>https://dev.to/azure/is-there-a-pattern-to-collaboration-1lio</link>
      <guid>https://dev.to/azure/is-there-a-pattern-to-collaboration-1lio</guid>
      <description>&lt;h1&gt;
  
  
  Is there a pattern to collaboration?
&lt;/h1&gt;

&lt;p&gt;Development is a collaborative sport. But so much of it is an individual's journey through problems. While it is an open secret that more eyes on a piece of code, makes better code, what is it the stops us from implementing these collaboration practices while writing code?&lt;/p&gt;

&lt;p&gt;I wonder if it is the up-front cost versus the apparent rewards. Much like the concept of a positive externality (from economics) where, the overall good that say pair-programming has, or code reviewing before PR's does on the general app health, is not effectively correlated to the action. &lt;/p&gt;

&lt;p&gt;So is there a pattern you follow when it comes to collaboration?&lt;/p&gt;

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