<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Go Development on Bogdan&#39;s website</title>
    <link>https://ubogdan.com/categories/go-development/</link>
    <description>Recent content in Go Development on Bogdan&#39;s website</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 11 May 2026 20:58:43 +0200</lastBuildDate><atom:link href="https://ubogdan.com/categories/go-development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Creating Production-Ready CLI Tools with Go 1.22&#39;s Built-in Flags System</title>
      <link>https://ubogdan.com/2026/05/creating-production-ready-cli-tools-with-go-1.22s-built-in-flags-system/</link>
      <pubDate>Mon, 11 May 2026 20:58:43 +0200</pubDate>
      
      <guid>https://ubogdan.com/2026/05/creating-production-ready-cli-tools-with-go-1.22s-built-in-flags-system/</guid>
      <description>Introduction Command-line tools are the connective tissue of modern infrastructure. Deploy scripts, log scanners, health checkers, migration runners, and Kubernetes helpers are usually small programs that run unattended in CI pipelines, cron jobs, and incident-response terminals. A tool that fails with a cryptic stack trace at 3 AM, or silently accepts a typo&amp;rsquo;d option, costs real time and sometimes real money.
Go is a natural fit for CLIs. It compiles to a single binary, starts quickly, and cross-compiles with one environment variable.</description>
    </item>
    
  </channel>
</rss>
