<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on krash.dev</title><link>https://krash.dev/tags/automation/</link><description>Recent content in Automation on krash.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 14 Aug 2026 08:29:09 +0530</lastBuildDate><atom:link href="https://krash.dev/tags/automation/rss.xml" rel="self" type="application/rss+xml"/><item><title>Production Grade Bash Scripts</title><link>https://krash.dev/posts/writing-production-grade-bash-script/</link><pubDate>Wed, 16 Apr 2025 00:00:00 +0000</pubDate><guid>https://krash.dev/posts/writing-production-grade-bash-script/</guid><description>&lt;p&gt;Most shell scripts start innocent, just a few lines to glue things together. Blink twice, and it’s deploying infrastructure, rotating secrets, restarting servers, and possibly provisioning a small nation-state. It’s doing things for the people, by the people, held together by &lt;code&gt;echo&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;This isn’t another “bash scripting 101” tutorial. You already know how to loop over a list and grep things. This is about writing scripts that survive real-world conditions: bad input, missing dependencies, flaky networks, and humans.&lt;/p&gt;</description></item></channel></rss>