<?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>Buenas Prácticas on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/buenas-pr%C3%A1cticas/</link><description>Recent content in Buenas Prácticas 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/buenas-pr%C3%A1cticas/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><item><title>Never write for-loops again</title><link>http://karpoke.ignaciocano.com/2016/12/12/never-write-for-loops-again/</link><pubDate>Mon, 12 Dec 2016 00:22:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2016/12/12/never-write-for-loops-again/</guid><description>&lt;blockquote&gt;
&lt;p&gt;It’s been a while since I started exploring the amazing language features in
Python. At the beginning, it’s just a challenge I gave myself to practice
using more language features instead of those I learned from other
programming language. And things are just getting more fun! Not only the code
become shorter and cleaner, but also code looks more structured and
disciplined. I’ll get into those benefits more in this article.&lt;/p&gt;</description></item><item><title>Bullet proofing Django models</title><link>http://karpoke.ignaciocano.com/2016/11/07/bullet-proofing-django-models/</link><pubDate>Mon, 07 Nov 2016 01:17:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2016/11/07/bullet-proofing-django-models/</guid><description>&lt;p&gt;Related:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;We recently added a bank account like functionality into one of our products.
During the development we encountered some textbook problems and I thought it
can be a good opportunity to go over some of the patterns we use in our
Django models.
This article was written in the order in which we usually address new
problems:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Define the business requirements.&lt;/li&gt;
&lt;li&gt;Write down a naive implementation and model definition.&lt;/li&gt;
&lt;li&gt;Challenge the solution.&lt;/li&gt;
&lt;li&gt;Refine and repeat.&lt;/li&gt;
&lt;/ol&gt;
&lt;/blockquote&gt;
&lt;p&gt;» Haki Benita | &lt;a href="https://medium.com/@hakibenita/bullet-proofing-django-models-c080739be4e#.pqtppqgoj"&gt;medium.com&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>