<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Shell Script Development on Under the Anvil</title>
		<link>https://blog.thetextsmith.com/tags/shell-script-development/</link>
		<description>Recent content in Shell Script Development on Under the Anvil</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 27 Jul 2026 17:27:20 +0200</lastBuildDate>
		
			<atom:link href="https://blog.thetextsmith.com/tags/shell-script-development/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>From One-Liners to Utilities: When Should a Shell Command Become a Script?</title>
				<link>https://blog.thetextsmith.com/the-workshop/from-one-liners-to-utilities-when-should-a-shell-command-become-a-script/</link>
				<pubDate>Mon, 27 Jul 2026 17:27:20 +0200</pubDate>
				<guid>https://blog.thetextsmith.com/the-workshop/from-one-liners-to-utilities-when-should-a-shell-command-become-a-script/</guid>
				<description>In a previous post, I discussed handling personal frustration through building my own utility, and learning programming in the process. The question now is: at what point should a group of commands, ofen represented as one-liners, be turned into a script?</description>
			</item>
	</channel>
</rss>
