<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Standards on Townsourced Tech Blog</title>
    <link>https://tech.townsourced.com/tags/standards/</link>
    <description>Recent content in Standards on Townsourced Tech Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.</copyright>
    <lastBuildDate>Mon, 30 Jul 2018 10:12:00 +0000</lastBuildDate>
    
	<atom:link href="https://tech.townsourced.com/tags/standards/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>When Naming Is Important, and When It&#39;s Not</title>
      <link>https://tech.townsourced.com/post/when-naming-is-important-and-when-its-not/</link>
      <pubDate>Mon, 30 Jul 2018 10:12:00 +0000</pubDate>
      
      <guid>https://tech.townsourced.com/post/when-naming-is-important-and-when-its-not/</guid>
      <description>Like Neanderthals Grunting and Pointing at Cave Paintings The other day a junior dev walked up to my desk and ask for some help troubleshooting a deadlocking issue he was seeing. I wasn&amp;rsquo;t familiar with the details of his process, so he proceeded to explain to me how the data was modeled, and how it flowed from one process to the next and was modified along the way.
The process was complicated enough that I wasn&amp;rsquo;t able to build a clear picture of the process in my head.</description>
    </item>
    
  </channel>
</rss>