<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Technical Writing on code.kiwi.com</title><link>https://code.kiwi.com/tag/technical-writing/</link><description>Recent content in Technical Writing on code.kiwi.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 17 Mar 2023 18:40:28 +0000</lastBuildDate><atom:link href="https://code.kiwi.com/tag/technical-writing/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></channel></rss>