<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Viper on Despair Driven Development</title><link>https://despairdrivendevelopment.com/tags/viper/</link><description>Recent content in Viper on Despair Driven Development</description><generator>Hugo</generator><language>en-us</language><managingEditor>matt@fitzpatricksoftware.com (Matthew FitzPatrick)</managingEditor><webMaster>matt@fitzpatricksoftware.com (Matthew FitzPatrick)</webMaster><lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://despairdrivendevelopment.com/tags/viper/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a CLI Tool in Go: Part 2 - Commands &amp; Config</title><link>https://despairdrivendevelopment.com/posts/go-cli-part-2-commands/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><author>matt@fitzpatricksoftware.com (Matthew FitzPatrick)</author><guid>https://despairdrivendevelopment.com/posts/go-cli-part-2-commands/</guid><description>&lt;p&gt;In &lt;a href="https://despairdrivendevelopment.com/posts/go-cli-part-1-setup/"&gt;Part 1&lt;/a&gt;, we set up the skeleton. Now let&amp;rsquo;s give it bones.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll add a &lt;code&gt;scan&lt;/code&gt; command that reads a config file and does something marginally useful.&lt;/p&gt;</description></item></channel></rss>