<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Git on The IT Hollow</title>
    <link>https://theithollow.com/tags/git/</link>
    <description>Recent content in Git on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Nov 2018 14:55:55 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Quality Checking Infrastructure-as-Code</title>
      <link>https://theithollow.com/2018/11/05/quality-checking-infrastructure-as-code/</link>
      <pubDate>Mon, 05 Nov 2018 14:55:55 +0000</pubDate>
      <guid>https://theithollow.com/2018/11/05/quality-checking-infrastructure-as-code/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;ve been doing application development for long, having tools in place to check the health of your code is probably not a new concept. However, if you&amp;rsquo;re jumping into something like Cloud and you&amp;rsquo;ve been an infrastructure engineer, this may be a foreign concept to you. Isn&amp;rsquo;t it bad enough that you&amp;rsquo;ve started learning Git, JSON, YAML, APIs etc on top of your existing skill sets? Well, take some lessons from the application teams and you may well find that you&amp;rsquo;re improving your processes and reducing the technical debt and time to provision infrastructure as code resources as well.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
