<?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 Aman Verma</title><link>https://amanverma.dev/tags/go/</link><description>Recent content in Go on Aman Verma</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 31 Jan 2025 23:35:09 +0530</lastBuildDate><atom:link href="https://amanverma.dev/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>On code samples that drift</title><link>https://amanverma.dev/posts/on-code-samples-that-drift/</link><pubDate>Fri, 31 Jan 2025 23:35:09 +0530</pubDate><guid>https://amanverma.dev/posts/on-code-samples-that-drift/</guid><description>&lt;p&gt;The code sample in your README is wrong. Not catastrophically — just enough to make the next person reading it run &lt;code&gt;go build&lt;/code&gt;, get an error, and wonder if the problem is them.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve been bitten by this enough times to build a tool around it. But the tool isn&amp;rsquo;t the interesting part. The interesting part is &lt;em&gt;how&lt;/em&gt; this happens, and what it says about the shape of your documentation.&lt;/p&gt;</description></item></channel></rss>