<?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>Anti-Patterns on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/anti-patterns/</link><description>Recent content in Anti-Patterns on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Wed, 25 Nov 2020 23:44:20 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/anti-patterns/index.xml" rel="self" type="application/rss+xml"/><item><title>Anti-patterns You Should Avoid in Your Code</title><link>http://karpoke.ignaciocano.com/2020/11/25/anti-patterns-you-should-avoid-in-your-code/</link><pubDate>Wed, 25 Nov 2020 23:44:20 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/11/25/anti-patterns-you-should-avoid-in-your-code/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Every developer wants to write structured, simply planned, and nicely
commented code. There are even a myriad of design patterns that give us
clear rules to follow, and a framework to keep in mind. But we can still
find anti-patterns in software that&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» freeCodeCamp.org | &lt;a href="https://www.freecodecamp.org/news/antipatterns-to-avoid-in-code/"&gt;freecodecamp.org&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>