<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Kotka</title>
    <link>http://kotka.de/blog/</link>
    <description>About Clojure… What else?</description>
    <language>en</language>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <generator>blosxom/2.1.2</generator>

    <item>
      <title>Did you know about some?</title>
      <pubDate>Wed, 01 Sep 2010 23:33:00 +0200</pubDate>
      <link>http://kotka.de/blog/2010/09/Did_you_know_VIII.html</link>
      <category>/2010/09</category>
      <guid isPermaLink="true">http://kotka.de/blog/2010/09/Did_you_know_VIII.html</guid>
      <description>&lt;p&gt;Every once in a while someone asks on the &lt;a href=&quot;http://groups.google.com/group/clojure&quot;&gt;Clojure group&lt;/a&gt;
why &lt;code&gt;(contains? [:a :b :c] :a)&lt;/code&gt; returns &lt;code&gt;false&lt;/code&gt;. In the following heated
discussions about semantics (yeah! a discussion about semantics!) people
always suggest to add a &lt;code&gt;linear-search&lt;/code&gt; to Clojure. What they miss:
&lt;code&gt;linear-search&lt;/code&gt; is already there.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://kotka.de/blog/2010/09/Did_you_know_VIII.html&quot; class=&quot;seemore&quot;&gt;See more ...&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Should we prefer dynamic behaviour?</title>
      <pubDate>Mon, 23 Aug 2010 22:39:00 +0200</pubDate>
      <link>http://kotka.de/blog/2010/08/Static_vs_Dynamic.html</link>
      <category>/2010/08</category>
      <guid isPermaLink="true">http://kotka.de/blog/2010/08/Static_vs_Dynamic.html</guid>
      <description>&lt;p&gt;Clojure is a dynamic programming language. This is a huge plus in my
opinion. It really makes fast development easy. Especially when fishing
in troubled waters for a rapid prototype (or when you are a lone
fighter).&lt;/p&gt;

&lt;p&gt;However dynamic behaviour usually comes at a runtime cost. Clojure
provides several means to gain speed at cost of its dynamic nature. One
example are type hints. Another – not so obvious – example are inline
definitions of protocol functions in a &lt;code&gt;defrecord&lt;/code&gt;. What are the
trade-offs? And what should be the default?&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://kotka.de/blog/2010/08/Static_vs_Dynamic.html&quot; class=&quot;seemore&quot;&gt;See more ...&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Did you know about the importance of being first?</title>
      <pubDate>Mon, 02 Aug 2010 23:45:00 +0200</pubDate>
      <link>http://kotka.de/blog/2010/08/Did_you_know_VII.html</link>
      <category>/2010/08</category>
      <guid isPermaLink="true">http://kotka.de/blog/2010/08/Did_you_know_VII.html</guid>
      <description>&lt;p&gt;Last week, I had the chance of attending the Clojure dojo at the Thoughtworks
office in London. It was great to see so many people enjoying to work with
Clojure. Unfortunately chances are rather low to put up something similar here
in the Rhein-Main region. &lt;em&gt;sigh&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;However, what I really want to talk about is a question which arose during the
dojo. In fact this question has been raised several times and I think it can&apos;t
hurt to shed some more light on this issue: „How to order the arguments of
your functions?“&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://kotka.de/blog/2010/08/Did_you_know_VII.html&quot; class=&quot;seemore&quot;&gt;See more ...&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Did you know about version numbers?</title>
      <pubDate>Sun, 25 Jul 2010 00:36:00 +0200</pubDate>
      <link>http://kotka.de/blog/2010/07/Did_you_know_VI.html</link>
      <category>/2010/07</category>
      <guid isPermaLink="true">http://kotka.de/blog/2010/07/Did_you_know_VI.html</guid>
      <description>&lt;p&gt;In our todays installment of my little „Did you know“-series we won&apos;t
look at Clojure itself but an important infrastructure topic.&lt;/p&gt;

&lt;p&gt;The Clojure ecosystem is growing steadily. New libraries spawn every
day. This is a Good Thing™. Tools like &lt;a href=&quot;http://maven.apache.org/&quot;&gt;maven&lt;/a&gt;, &lt;a href=&quot;http://www.gradle.org&quot;&gt;gradle&lt;/a&gt;, &lt;a href=&quot;http://github.com/technomancy/leiningen&quot;&gt;leiningen&lt;/a&gt;
and &lt;a href=&quot;http://ant.apache.org/ivy/&quot;&gt;ivy&lt;/a&gt; make life easier for the developer who intends to use these new
libraries. However library developers should pay attention to some details.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://kotka.de/blog/2010/07/Did_you_know_VI.html&quot; class=&quot;seemore&quot;&gt;See more ...&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>ClojureCheck is back!</title>
      <pubDate>Sun, 13 Jun 2010 22:28:00 +0200</pubDate>
      <link>http://kotka.de/blog/2010/06/ClojureCheck_is_back.html</link>
      <category>/2010/06</category>
      <guid isPermaLink="true">http://kotka.de/blog/2010/06/ClojureCheck_is_back.html</guid>
      <description>&lt;p&gt;&lt;a href=&quot;http://bitbucket.org/kotarak/clojurecheck&quot;&gt;ClojureCheck&lt;/a&gt; is back.
It brings specification based testing to Clojure and integrates
(almost) seamless with &lt;code&gt;clojure.test&lt;/code&gt;. So what does specification
based testing mean and how does it help you?&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://kotka.de/blog/2010/06/ClojureCheck_is_back.html&quot; class=&quot;seemore&quot;&gt;See more ...&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
