<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code on code.kiwi.com</title><link>https://code.kiwi.com/tag/code/</link><description>Recent content in Code on code.kiwi.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 23 Mar 2023 19:00:05 +0000</lastBuildDate><atom:link href="https://code.kiwi.com/tag/code/index.xml" rel="self" type="application/rss+xml"/><item><title>5 Reasons to Write a Document Before Writing Code</title><link>https://code.kiwi.com/articles/5-reasons-to-write-a-document-before-writing-code/</link><pubDate>Wed, 22 Apr 2020 18:39:00 +0000</pubDate><guid>https://code.kiwi.com/articles/5-reasons-to-write-a-document-before-writing-code/</guid><description>&lt;p&gt;Writing a proper design document is often frowned upon. Whether it is an RFC or a problem specification — it doesn’t matter what you call it — the usual reaction is:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Ain’t nobody got time for that. We need to write code.&lt;/p&gt;</description></item><item><title>Say goodbye to loops with ‘reduce’ ????</title><link>https://code.kiwi.com/articles/say-goodbye-to-loops-with-reduce-%F0%9F%91%8B/</link><pubDate>Thu, 28 Mar 2019 21:18:00 +0000</pubDate><guid>https://code.kiwi.com/articles/say-goodbye-to-loops-with-reduce-%F0%9F%91%8B/</guid><description>&lt;p&gt;If you’re starting with functional programming and don’t know where to continue after &lt;code&gt;map&lt;/code&gt; and &lt;code&gt;filter&lt;/code&gt;, go with &lt;code&gt;reduce&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://code.kiwi.com/images/media/b2901aab410d7ff2d493f31831acb3ff9d5f0b41ab490ef0533c8151153f3e89.webp" alt=""&gt;&lt;/p&gt;
&lt;p&gt;–Do you insist on using the image of the cat? –Yes, I do. Reflects the essence of functional programming. Source: &lt;a href="https://farm6.staticflickr.com/5185/5619954191_565779cf5d_b.jpg"&gt;https://farm6.staticflickr.com/5185/5619954191_565779cf5d_b.jpg&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Code Design Principles for Public APIs of Modules</title><link>https://code.kiwi.com/articles/code-design-principles-for-public-apis-of-modules/</link><pubDate>Fri, 13 Oct 2017 22:17:00 +0000</pubDate><guid>https://code.kiwi.com/articles/code-design-principles-for-public-apis-of-modules/</guid><description>&lt;p&gt;&lt;em&gt;The following article is from Kiwi.com’s internal engineering handbook. We thought it could come in handy for others as well, so we decided to share it with the world here.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This document should leave you with some idea on how to approach problems where you have to create a new module from scratch, or come up with a way to completely redesign an existing one.&lt;/p&gt;</description></item></channel></rss>