<?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>Revisión De Código on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/revisi%C3%B3n-de-c%C3%B3digo/</link><description>Recent content in Revisión De Código on Karpoke - Just Another Blog</description><generator>Hugo -- 0.159.0</generator><language>es</language><lastBuildDate>Sun, 23 Nov 2014 12:33:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/revisi%C3%B3n-de-c%C3%B3digo/index.xml" rel="self" type="application/rss+xml"/><item><title>This is how we ZenPayroll: Our Development Workflow</title><link>http://karpoke.ignaciocano.com/2014/11/23/this-is-how-we-zenpayroll-our-development-workflow/</link><pubDate>Sun, 23 Nov 2014 12:33:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2014/11/23/this-is-how-we-zenpayroll-our-development-workflow/</guid><description>&lt;blockquote&gt;
&lt;p&gt;A lot of engineers looking to join ZenPayroll are interested in
hearing more about our development workflow. Put more simply, how do
ZenPayrollers write software? The answer to that is constantly
changing, as we’re always refining our workflows to fit our ever
changing needs, but I’ll cover in some detail the way we do things
today.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» Edward Kim | &lt;a href="http://engineering.zenpayroll.com/this-is-how-we-zenpayroll-our-development-workflow/"&gt;engineering.zenpayroll.com&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>