<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ideas on queil.net</title>
    <link>https://queil.net/tags/ideas/</link>
    <description>Recent content in Ideas on queil.net</description>
    <generator>Hugo</generator>
    <language>en-uk</language>
    <lastBuildDate>Sun, 16 Jun 2019 10:52:57 +0100</lastBuildDate>
    <atom:link href="https://queil.net/tags/ideas/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Thinking</title>
      <link>https://queil.net/ideas/2019/thinking/</link>
      <pubDate>Sun, 16 Jun 2019 10:52:57 +0100</pubDate>
      <guid>https://queil.net/ideas/2019/thinking/</guid>
      <description>&lt;p&gt;Thinking is the vital part of software development process. It raises questions. It is the &lt;em&gt;fail fast&lt;/em&gt; principle taken to the extreme. I&amp;rsquo;d extend the popular &amp;ldquo;&lt;em&gt;code the right thing&lt;/em&gt;&amp;rdquo; to &amp;ldquo;&lt;strong&gt;define what the right thing is, determine if code is the best solution in the first place, and then, if the answer is &lt;em&gt;yes&lt;/em&gt;, build a solid mental model, and finally start coding the right thing&lt;/strong&gt;&amp;rdquo;. Building a mental model may, (and often does), involve coding, and usually it&amp;rsquo;s an iterative process. Especially, when we explore an unknown domain and the model rapidly evolves. However, code is treated here as a &lt;em&gt;thinking tool&lt;/em&gt; rather than the final product. It could be compared to sketching before putting any paint on the canvas. It&amp;rsquo;s easy and cheap to modify a sketch where is much more difficult to alter a ready painting.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
