<?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 Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/refactoring/</link><description>Recent content in Refactoring on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Mon, 02 Mar 2026 12:00:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/refactoring/index.xml" rel="self" type="application/rss+xml"/><item><title>Code Rewriting With AI and TDD</title><link>http://karpoke.ignaciocano.com/2026/03/02/code-rewriting-with-ai-and-tdd/</link><pubDate>Mon, 02 Mar 2026 12:00:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2026/03/02/code-rewriting-with-ai-and-tdd/</guid><description>&lt;blockquote&gt;
&lt;p&gt;In this article, we explore TDD and AI to rewrite projects with
architectural debt, and how TDD in such cases can serve as a guardrail
against hallucinations.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» dzone.com | &lt;a href="https://dzone.com/articles/code-rewriting-with-ai-and-tdd"&gt;dzone.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>PyBites: When to refactor your code?</title><link>http://karpoke.ignaciocano.com/2023/08/12/pybites-when-to-refactor-your-code/</link><pubDate>Sat, 12 Aug 2023 02:21:51 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2023/08/12/pybites-when-to-refactor-your-code/</guid><description>&lt;blockquote&gt;
&lt;p&gt;PyBites: When to refactor your code?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» pybit.es | &lt;a href="https://pybit.es/articles/when-to-refactor-your-code/"&gt;pybit.es&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Strategic Refactoring: A Roadmap for Tackling Technical Debt Head-On</title><link>http://karpoke.ignaciocano.com/2023/08/10/strategic-refactoring-a-roadmap-for-tackling-technical-debt-head-on/</link><pubDate>Thu, 10 Aug 2023 19:56:04 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2023/08/10/strategic-refactoring-a-roadmap-for-tackling-technical-debt-head-on/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Explore strategies to tackle technical debt and enhance code quality.
Learn to balance business goals with refactoring for long-term success.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» Ivan Novak | &lt;a href="https://www.ivannovak.com/blog/tackling-technical-debt-a-strategic-approach-to-refactoring"&gt;ivannovak.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>How to Find the Stinky Parts of Your Code [Part XXXIX]</title><link>http://karpoke.ignaciocano.com/2023/06/20/how-to-find-the-stinky-parts-of-your-code-part-xxxix/</link><pubDate>Tue, 20 Jun 2023 10:59:23 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2023/06/20/how-to-find-the-stinky-parts-of-your-code-part-xxxix/</guid><description>&lt;blockquote&gt;
&lt;p&gt;It smells because there are likely many instances where it could be
edited or improved.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» hackernoon.com | &lt;a href="https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxxix"&gt;hackernoon.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>La regla del tres y la refactorización</title><link>http://karpoke.ignaciocano.com/2023/05/02/la-regla-del-tres-y-la-refactorizacion/</link><pubDate>Tue, 02 May 2023 15:01:03 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2023/05/02/la-regla-del-tres-y-la-refactorizacion/</guid><description>&lt;blockquote&gt;
&lt;p&gt;La regla del tres es una regla muy común cuando estamos trabajando con
código y queremos refactorizar partes del código que sean idénticas o
muy muy similar&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» Cecilio Álvarez Caules | &lt;a href="https://www.arquitecturajava.com/la-regla-del-tres-y-la-refactorizacion/"&gt;arquitecturajava.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Python — Duplicate For Loops</title><link>http://karpoke.ignaciocano.com/2023/04/19/python-duplicate-for-loops/</link><pubDate>Wed, 19 Apr 2023 15:33:52 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2023/04/19/python-duplicate-for-loops/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Python — Duplicate For Loops&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» hackernoon.com | &lt;a href="https://hackernoon.com/python-duplicate-for-loops"&gt;hackernoon.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>How to Find the Stinky Parts of Your Code [Part XXI]</title><link>http://karpoke.ignaciocano.com/2022/07/24/how-to-find-the-stinky-parts-of-your-code-part-xxi/</link><pubDate>Sun, 24 Jul 2022 12:15:37 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2022/07/24/how-to-find-the-stinky-parts-of-your-code-part-xxi/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Code smells are a classic. It smells because there are likely many
instances where it could be edited or improved.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» hackernoon.com | &lt;a href="https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxi"&gt;hackernoon.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>What is "Code Refactoring"?</title><link>http://karpoke.ignaciocano.com/2021/12/13/what-is-code-refactoring/</link><pubDate>Mon, 13 Dec 2021 23:40:04 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2021/12/13/what-is-code-refactoring/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Recently I&amp;rsquo;ve been dealing with code refactoring in my workplace, and
therefore I thought about&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/maddy/what-is-code-refactoring-26nd"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>What does the Open-Closed Principle mean for refactoring?</title><link>http://karpoke.ignaciocano.com/2021/07/16/what-does-the-open-closed-principle-mean-for-refactoring/</link><pubDate>Fri, 16 Jul 2021 14:24:07 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2021/07/16/what-does-the-open-closed-principle-mean-for-refactoring/</guid><description>&lt;blockquote&gt;
&lt;p&gt;In his 1988 book, Object-Oriented Software Construction, pro&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» Alex Bunardzic | &lt;a href="https://opensource.com/article/21/7/open-closed-principle-refactoring"&gt;opensource.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>How to write clean code units (functions and methods)</title><link>http://karpoke.ignaciocano.com/2021/04/30/how-to-write-clean-code-units-functions-and-methods/</link><pubDate>Fri, 30 Apr 2021 08:45:42 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2021/04/30/how-to-write-clean-code-units-functions-and-methods/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Code units at the edges of your application should be small, independent
and only do one thing&amp;hellip;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/sargalias/how-to-write-clean-code-units-functions-and-methods-16l2"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>FizzBuzz Refactoring Challenge with Open/Closed Principle</title><link>http://karpoke.ignaciocano.com/2020/06/04/fizzbuzz-refactoring-challenge-with-open-closed-principle/</link><pubDate>Thu, 04 Jun 2020 21:07:28 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/06/04/fizzbuzz-refactoring-challenge-with-open-closed-principle/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Introduction Have you ever heard of the FizzBuzz refactoring challenge?
I encountered it&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/olivermensahdev/fizzbuzz-refactoring-challenge-with-open-closed-principle-4m42"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Gilded Rose 4</title><link>http://karpoke.ignaciocano.com/2020/04/20/gilded-rose-4/</link><pubDate>Mon, 20 Apr 2020 20:35:08 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/04/20/gilded-rose-4/</guid><description>&lt;blockquote&gt;
&lt;p&gt;This is RonJeffries.com, the combination of new articles, XProgramming,
SameElephant, and perhaps even some new items never before contemplated.
&lt;br/&gt;Copyright © 1998-forever Ronald E Jeffries&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» ronjeffries.com | &lt;a href="https://ronjeffries.com/articles/020-01ff/gilded-rose-4/"&gt;ronjeffries.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>10 practices for readable code</title><link>http://karpoke.ignaciocano.com/2018/09/19/10-practices-for-readable-code/</link><pubDate>Wed, 19 Sep 2018 19:59:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2018/09/19/10-practices-for-readable-code/</guid><description>&lt;blockquote&gt;
&lt;p&gt;I’ve been writing code for 20 years. During that time I’ve worked with 17
teams coding different languages to build hundreds of projects. These
include everything from a simple blog site, to APIs supporting 3,000
requests/second, to top selling apps. From these experiences, combined with
the books I’ve read, it’s become apparent to me what matters most in code:
readability.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» Jason McCreary | &lt;a href="http://jason.pureconcepts.net/2018/09/practices-write-readable-code-less-complex/"&gt;jason.pureconcepts.net&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Deuda técnica</title><link>http://karpoke.ignaciocano.com/2012/06/04/deuda-tecnica/</link><pubDate>Mon, 04 Jun 2012 14:12:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/06/04/deuda-tecnica/</guid><description>&lt;blockquote&gt;
&lt;p&gt;¿Qué desarrollador de software nunca ha estado una semana programando
a toda velocidad, casi sin saber que hace, ya que la fecha de entrega
está cerca y todo tiene que estar terminado ”para ayer”? ¿Quién no se
ha encontrado en la situación de saber que está programando una
chapuza, pensando que otro día lo mejorará, y ese día nunca llega?
¿Quién alguna vez, al ver una porción de código fuente no ha exclamado
indignado: ¡qué narices hace este código! o ¡quién leches lo ha
programado!?&lt;/p&gt;
&lt;p&gt;A todo este código lo solemos calificar como chapuzas, apaños, ñapas,
mierdecillas¦ Su problema es que, por lo general, se va extendiendo de
forma exponencial y acumulándose a lo largo del desarrollo de un
proyecto. Y en consecuencia tenemos como resultado un código fuente
que es muy difícil de mantener, extender y reutilizar; y un aplicativo
que funcionalmente tiene problemas.&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>