<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Go on Project Wintermute</title><link>https://wintermutecore.com/tags/go/</link><description>Recent content in Go on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 09 Apr 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://wintermutecore.com/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating Go test helpers from Azure SDK v1 to v2 (track 2)</title><link>https://wintermutecore.com/posts/azure-sdk-v2-go-migration/</link><pubDate>Thu, 09 Apr 2026 09:00:00 +0200</pubDate><guid>https://wintermutecore.com/posts/azure-sdk-v2-go-migration/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR.&lt;/strong&gt; Track 2 of &lt;code&gt;azure-sdk-for-go&lt;/code&gt; is not a search-and-replace from track 1. Plan for a credential rework, a client factory pass, and a nil-safety sweep on every pointer chain. Lock the patterns in CI lints so the next batch ships cleaner than the previous one.&lt;/p&gt;
&lt;p&gt;Microsoft &lt;code&gt;azure-sdk-for-go&lt;/code&gt; track 1 packages (rooted at &lt;code&gt;github.com/Azure/azure-sdk-for-go/services/...&lt;/code&gt;) have been on the deprecation path for a while. Track 2 (the &lt;code&gt;armXxx&lt;/code&gt; packages under &lt;code&gt;github.com/Azure/azure-sdk-for-go/sdk/...&lt;/code&gt;) is the supported surface and the only one with active fixes.&lt;/p&gt;</description></item><item><title>Tag-based AWS resource cleanup: patterns that actually scale</title><link>https://wintermutecore.com/posts/aws-tag-based-resource-cleanup/</link><pubDate>Fri, 03 Apr 2026 11:00:00 +0200</pubDate><guid>https://wintermutecore.com/posts/aws-tag-based-resource-cleanup/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR.&lt;/strong&gt; Name and time filters are not enough for safe AWS bulk cleanup. Use tags as the primary signal, expect &lt;code&gt;ListTagsForResource&lt;/code&gt; to be your bottleneck, enforce tagging at provisioning time, and run an audit job that flags untagged resources so the policy stays honest.&lt;/p&gt;
&lt;p&gt;The &amp;ldquo;delete a lot of AWS resources at once&amp;rdquo; problem shows up in every account: CI sandboxes, expired test estates, dev environments forgotten about, ad-hoc reproductions left behind. Bulk cleanup tools that target this exist and work well. Used carelessly any of them is a footgun. Used carefully with tag filtering, they become one of the most useful pieces of cost discipline you can ship.&lt;/p&gt;</description></item><item><title>Speeding up GitHub Actions lint pipelines for large Go codebases</title><link>https://wintermutecore.com/posts/go-ci-lint-pipeline-optimisation/</link><pubDate>Thu, 12 Feb 2026 10:00:00 +0200</pubDate><guid>https://wintermutecore.com/posts/go-ci-lint-pipeline-optimisation/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR.&lt;/strong&gt; Lint on a large Go monorepo went from 63 seconds to about 25 seconds on warm cache, with macOS skipped on branches. Five changes: concurrency group, conditional OS matrix, combined cache restore and save, explicit &lt;code&gt;go mod download&lt;/code&gt;, and incremental &lt;code&gt;golangci-lint --new-from-rev&lt;/code&gt;. None require a self-hosted runner.&lt;/p&gt;
&lt;p&gt;A large Go codebase makes the CI lint stage the part developers feel most: every push, on every branch. Lint feedback that takes a minute and a half kills iteration speed and quietly trains people to push less often, which is the opposite of what you want.&lt;/p&gt;</description></item></channel></rss>