<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Refactoring on Jake Worth</title><link>https://jakeworth.com/tags/refactoring/</link><description>Recent content in Refactoring on Jake Worth</description><image><title>Jake Worth</title><url>https://jakeworth.com/twittercard.png</url><link>https://jakeworth.com/twittercard.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 01 Feb 2026 12:46:52 -0500</lastBuildDate><atom:link href="https://jakeworth.com/tags/refactoring/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Unabstract an Abstraction</title><link>https://jakeworth.com/posts/how-to-unabstract-an-abstraction/</link><pubDate>Sun, 01 Feb 2026 12:46:52 -0500</pubDate><guid>https://jakeworth.com/posts/how-to-unabstract-an-abstraction/</guid><description>&lt;p&gt;Abstractions in code are easy to add and challenging to remove. Sometimes we feel stuck with them. But the good news is, you can back out of almost any abstraction with the right mindset.&lt;/p&gt;</description></item><item><title>Naive Implementation: The Art of Artless Programming</title><link>https://jakeworth.com/posts/naive-implementation/</link><pubDate>Thu, 23 Jun 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/naive-implementation/</guid><description>&lt;p&gt;A naive implementation is a programming technique that prioritizes imperfect
shortcuts for the sake of speed, simplicity, or lack of knowledge.&lt;/p&gt;</description></item><item><title>How to Make Renames Easy</title><link>https://jakeworth.com/posts/make-renames-easy/</link><pubDate>Tue, 22 Mar 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/make-renames-easy/</guid><description>&lt;p&gt;Names in software are hard. But what&amp;rsquo;s worse than a bad name? Sticking with it
because you can&amp;rsquo;t change it. I want us all to be able to effortlessly and
fearlessly fix bad names. That&amp;rsquo;s the topic of this post.&lt;/p&gt;</description></item><item><title>Write Better Code by Knowing When Not To Refactor</title><link>https://jakeworth.com/posts/when-should-i-not-refactor/</link><pubDate>Thu, 26 Aug 2021 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/when-should-i-not-refactor/</guid><description>&lt;p&gt;When I review code, I sometimes request that refactoring changes be removed.
Even when I think the changes are are objective improvements, and even when
they support my personal preferences. My reasoning? Refactors are not free.&lt;/p&gt;</description></item></channel></rss>