<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Testing Blog</title>
    <link>https://learn.panoply.io/ab5467zx</link>
    <description>Something something description</description>
    <language>en</language>
    <pubDate>Thu, 06 Sep 2018 07:19:41 GMT</pubDate>
    <dc:date>2018-09-06T07:19:41Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Third Clone: Do's And Don't's (clone)</title>
      <link>https://learn.panoply.io/ab5467zx/dos-and-donts-in-data-collection-and-distribution-1-0-0</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://learn.panoply.io/ab5467zx/dos-and-donts-in-data-collection-and-distribution-1-0-0" title="" class="hs-featured-image-link"&gt; &lt;img src="https://learn.panoply.io/hubfs/Copy%20of%20EMAIL%20TEMPLATE%20MASTER%20600x267-AS.png" alt="Copy of EMAIL TEMPLATE MASTER 600x267-AS" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Anybody who hangs out in IT or data science circles will invariably become familiar with the acronym GIGO. GIGO stands for “garbage in, garbage out” (or “good in, good out,” depending on who you ask). But semantics aside, it’s a really good reminder about how data quality - including its collection and distribution - can have a noticeable impact on your analytics. So let’s look at a couple areas where engineers and analysts run into GIGO pitfalls - and how we can avoid them.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://learn.panoply.io/ab5467zx/dos-and-donts-in-data-collection-and-distribution-1-0-0" title="" class="hs-featured-image-link"&gt; &lt;img src="https://learn.panoply.io/hubfs/Copy%20of%20EMAIL%20TEMPLATE%20MASTER%20600x267-AS.png" alt="Copy of EMAIL TEMPLATE MASTER 600x267-AS" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Anybody who hangs out in IT or data science circles will invariably become familiar with the acronym GIGO. GIGO stands for “garbage in, garbage out” (or “good in, good out,” depending on who you ask). But semantics aside, it’s a really good reminder about how data quality - including its collection and distribution - can have a noticeable impact on your analytics. So let’s look at a couple areas where engineers and analysts run into GIGO pitfalls - and how we can avoid them.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=2548165&amp;amp;k=14&amp;amp;r=https%3A%2F%2Flearn.panoply.io%2Fab5467zx%2Fdos-and-donts-in-data-collection-and-distribution-1-0-0&amp;amp;bu=https%253A%252F%252Flearn.panoply.io%252Fab5467zx&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Panoply News</category>
      <category>Data Analysis</category>
      <category>Data Warehousing</category>
      <category>Working in Data</category>
      <pubDate>Thu, 06 Sep 2018 06:41:50 GMT</pubDate>
      <author>an@panoply.io (An Bui)</author>
      <guid>https://learn.panoply.io/ab5467zx/dos-and-donts-in-data-collection-and-distribution-1-0-0</guid>
      <dc:date>2018-09-06T06:41:50Z</dc:date>
    </item>
  </channel>
</rss>
