<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>bash on Yoann Bentz &lt;Yoone.eu&gt;</title>
    <link>/tags/bash/</link>
    <description>Recent content in bash on Yoann Bentz &lt;Yoone.eu&gt;</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Mar 2016 01:08:00 +0200</lastBuildDate><atom:link href="/tags/bash/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Good practices for writing shell scripts</title>
      <link>/article/good-practices-for-writing-shell-scripts/</link>
      <pubDate>Wed, 23 Mar 2016 01:08:00 +0200</pubDate>
      
      <guid>/article/good-practices-for-writing-shell-scripts/</guid>
      <description>I have seen so many messy shell scripts in my not so long life, and the reasons are always the same: &amp;ldquo;I’m the only one to use it&amp;rdquo;, &amp;ldquo;It’s meant to be used once&amp;rdquo;, etc. The problem is that in practice, those scripts are often reused or dug up months or even years later because they solved a problem similar to one you are having now. And when you have to understand a shell script that has been running in production for years and has been written by someone else, you will have to go through the famous &amp;ldquo;dusting&amp;rdquo; part i.</description>
    </item>
    
  </channel>
</rss>
