<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Quality on Architecture and Data Blog</title>
    <link>https://sadalage.com/tags/quality/</link>
    <description>Recent content in Quality on Architecture and Data Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>© 2026 Pramod Sadalage</copyright>
    <lastBuildDate>Thu, 24 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sadalage.com/tags/quality/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Collaborate to improve data quality</title>
      <link>https://sadalage.com/post/collaborate_to_improve_data_quality/</link>
      <pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate>
      
      <guid>https://sadalage.com/post/collaborate_to_improve_data_quality/</guid>
      <description>&lt;p&gt;When application has been running in production or uat for some time there are some bugs that get reported because of bad data quality. This data is either generated by the application or is created by data migration scripts, data conversion scripts. The application suffers with non-deterministic errors especially is some specific environments while similar errors are not noticed in other environments.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Data Quality and Code Quality</title>
      <link>https://sadalage.com/post/data_quality_and_code_quality/</link>
      <pubDate>Thu, 15 Feb 2007 00:00:00 +0000</pubDate>
      
      <guid>https://sadalage.com/post/data_quality_and_code_quality/</guid>
      <description>&lt;p&gt;Recently we had peculiar problem. Some of the data in the database was not being created in a proper fashion. Once we found that out we fixed the problem in the application. The customer still had the perception that the code is still broken, because the fixed code was now interacting with the data that was broken (since it was created much earlier by code that was broken). Data has a life of its own (more on this later)&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
