<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Refactoring on Antonio Cortés (DrZippie)</title><link>https://antoniocortes.com/en/tags/refactoring/</link><description>Recent content in Refactoring on Antonio Cortés (DrZippie)</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 25 Sep 2026 16:23:54 +0200</lastBuildDate><atom:link href="https://antoniocortes.com/en/tags/refactoring/index.xml" rel="self" type="application/rss+xml"/><item><title>go fix is back: modernizing Go code with a single command</title><link>https://antoniocortes.com/en/go-fix-modernizar-codigo/</link><pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/go-fix-modernizar-codigo/</guid><description>&lt;p&gt;If you&amp;rsquo;ve been writing Go for a few years, your code has layers. There&amp;rsquo;s an &lt;code&gt;interface{}&lt;/code&gt; from before &lt;code&gt;any&lt;/code&gt; existed, a &lt;code&gt;for i := 0; i &amp;lt; n; i++&lt;/code&gt; from before range over integers, some &lt;code&gt;x := x&lt;/code&gt; inside a loop to dodge the famous loop variable problem, and more than one chained &lt;code&gt;if&lt;/code&gt; that today would be a &lt;code&gt;min()&lt;/code&gt;. None of that is wrong. The language simply moved on and the code stayed where it was.&lt;/p&gt;</description></item></channel></rss>