<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Best Practices on Sai Ram&#39;s Blog</title>
    <link>https://sairam.dev/categories/best-practices/</link>
    <description>Recent content in Best Practices on Sai Ram&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2020. All rights reserved.</copyright>
    <lastBuildDate>Tue, 11 Apr 2017 23:30:05 +0530</lastBuildDate>
    
	<atom:link href="https://sairam.dev/categories/best-practices/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>A clean way of Deploying Code</title>
      <link>https://sairam.dev/post/2017-04-11-a-clean-way-of-deploying-code/</link>
      <pubDate>Tue, 11 Apr 2017 23:30:05 +0530</pubDate>
      
      <guid>https://sairam.dev/post/2017-04-11-a-clean-way-of-deploying-code/</guid>
      <description>Think of the tools like Makefile for C / C++ or yarn or nom in Javascript or bundle in Ruby or requirements.txt in Python or maven.xml in Java. Now the same applies to the operating system as well, in the operating system, you can add additional stuff outside a package manager which is hard to maintain or guess. You can do the same in the languages for libraries or ad-hoc code which was not intentionally to be present.</description>
    </item>
    
  </channel>
</rss>