<?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>Separación De Comandos Y Consultas on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/separaci%C3%B3n-de-comandos-y-consultas/</link><description>Recent content in Separación De Comandos Y Consultas on Karpoke - Just Another Blog</description><generator>Hugo -- 0.159.0</generator><language>es</language><lastBuildDate>Sat, 28 Oct 2017 16:42:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/separaci%C3%B3n-de-comandos-y-consultas/index.xml" rel="self" type="application/rss+xml"/><item><title>Coding with clarity</title><link>http://karpoke.ignaciocano.com/2017/10/28/coding-with-clarity/</link><pubDate>Sat, 28 Oct 2017 16:42:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2017/10/28/coding-with-clarity/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Working code isn’t necessarily good code. Your code also needs to be easy to
read, understand, and modify. It needs clarity, and to achieve that, it has
to be organized well, with careful planning and proper separation of ideas
taking place before you even open your code editor. Coding for clarity is
something that separates the great developers from the merely good, and there
are a few basic principles that can set you on that path.&lt;/p&gt;</description></item></channel></rss>