<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Goproxy on Brodie Kurczynski</title>
    <link>/tags/goproxy/</link>
    <description>Recent content in Goproxy on Brodie Kurczynski</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by-nc/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY-NC 4.0&lt;/a&gt;</copyright>
    <lastBuildDate>Tue, 15 Oct 2024 16:06:20 -0700</lastBuildDate>
    <atom:link href="/tags/goproxy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go Proxy</title>
      <link>/posts/2024/10/go-proxy/</link>
      <pubDate>Tue, 15 Oct 2024 16:06:20 -0700</pubDate>
      <guid>/posts/2024/10/go-proxy/</guid>
      <description>I&amp;rsquo;ve been using a lot of Go lately and I don&amp;rsquo;t have a whole lot of meaningful complaints about it, but I am still figuring out all the bastard gotchas. The most recent one I learned about the hard way was module caching using the Go proxy while building several microservices for a side project. Because it&amp;rsquo;s a side project, a lot of the planning has been done on a whiteboard and by writing shitty throw away code before implementing anything useful.</description>
    </item>
  </channel>
</rss>
