<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>dtvc87</title>
    <description/>
    <link>https://speakerdeck.com/dtvc87</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/dtvc87.rss"/>
    <lastBuildDate>2019-07-24 01:16:31 -0400</lastBuildDate>
    <item>
      <title>Static Analysis: enforcing code conventions</title>
      <description>It’s well known that as a team grows, the communication overhead increases geometrically until it takes up most of the time of the members. Static analysis can help us reduce the time cost, streamline the code review process, as well as to keep big teams synchronized. </description>
      <media:content url="https://files.speakerdeck.com/presentations/fb23ba4a8f924b8c9ff0e75aa1789b6a/preview_slide_0.jpg?13119730" type="image/jpeg" medium="image"/>
      <content:encoded>It’s well known that as a team grows, the communication overhead increases geometrically until it takes up most of the time of the members. Static analysis can help us reduce the time cost, streamline the code review process, as well as to keep big teams synchronized. </content:encoded>
      <pubDate>Tue, 23 Jul 2019 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/dtvc87/static-analysis-enforcing-code-conventions</link>
      <guid>https://speakerdeck.com/dtvc87/static-analysis-enforcing-code-conventions</guid>
    </item>
  </channel>
</rss>
