<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>WillAbides</title>
    <link>https://willabides.com/</link>
    <description>Recent content on WillAbides</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 10 Oct 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://willabides.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Gopher The Flag - A Mini Capture The Flag for Gophers</title>
      <link>https://willabides.com/posts/gopher-the-flag/</link>
      <pubDate>Tue, 10 Oct 2023 00:00:00 +0000</pubDate>
      <guid>https://willabides.com/posts/gopher-the-flag/</guid>
      <description>I went to GopherCon this year and did my first capture the flag. It was about as much fun as I&#39;ve had at a conference, and I will definitely do it again next year.&#xA;I&#39;ve been mulling another challenge since then, and today I took the time to put it together. I called it &amp;quot;gopher the flag&amp;quot;, but after seeing the code, &amp;quot;goto the flag&amp;quot; would have been a better name.</description>
    </item>
    <item>
      <title>Release Train - Continuous Releases Made Easy</title>
      <link>https://willabides.com/posts/release-train-continuous-releases-made-easy/</link>
      <pubDate>Tue, 01 Aug 2023 00:00:00 +0000</pubDate>
      <guid>https://willabides.com/posts/release-train-continuous-releases-made-easy/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://github.com/WillAbides/release-train&#34;&gt;Release Train&lt;/a&gt; is a tool to&#xA;automate creating a new release every time you merge a pull request. It is&#xA;inspired&#xA;by &lt;a href=&#34;https://github.com/semantic-release/semantic-release&#34;&gt;semantic-release&lt;/a&gt;, but&#xA;is easier to set up and use. Add a step to your GitHub workflow, start labeling&#xA;your pull requests, and you&#39;re riding the release train. No special incantations&#xA;are required for your commit messages, and your repo can remain npm-free.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Writing a Slog Handler Part 4: Final Thoughts</title>
      <link>https://willabides.com/posts/go-slog-handler-part-4/</link>
      <pubDate>Thu, 20 Jul 2023 03:00:00 +0000</pubDate>
      <guid>https://willabides.com/posts/go-slog-handler-part-4/</guid>
      <description>Wrapping up the slog series.</description>
    </item>
    <item>
      <title>Writing a Slog Handler Part 3: The Handler Revisited</title>
      <link>https://willabides.com/posts/go-slog-handler-part-3/</link>
      <pubDate>Thu, 20 Jul 2023 02:00:00 +0000</pubDate>
      <guid>https://willabides.com/posts/go-slog-handler-part-3/</guid>
      <description>Refactoring our slog handler to be more efficient.</description>
    </item>
    <item>
      <title>Writing a Slog Handler Part 2: The Handler</title>
      <link>https://willabides.com/posts/go-slog-handler-part-2/</link>
      <pubDate>Thu, 20 Jul 2023 01:00:00 +0000</pubDate>
      <guid>https://willabides.com/posts/go-slog-handler-part-2/</guid>
      <description>Continuing the introduction to Go&#39;s log/slog by writing a slog.Handler that outputs&#xA;human-readable logs.</description>
    </item>
    <item>
      <title>Writing a Slog Handler Part 1: The Wrapper</title>
      <link>https://willabides.com/posts/go-slog-handler-part-1/</link>
      <pubDate>Thu, 20 Jul 2023 00:00:00 +0000</pubDate>
      <guid>https://willabides.com/posts/go-slog-handler-part-1/</guid>
      <description>An introduction to Go&#39;s log/slog package. Writing a wrapper for a slog.Handler&#xA;that we can use in GitHub Actions.</description>
    </item>
  </channel>
</rss>
