<story><title>Clojure macros continue to surprise me</title><url>https://tonsky.me/blog/clojure-macros/</url></story><parent_chain></parent_chain><comment><author>lloydatkinson</author><text>I really enjoyed reading this, and I don&amp;#x27;t know Clojure at all. This is a problem I&amp;#x27;ve encountered several times while building design systems&amp;#x2F;component libraries. It&amp;#x27;s a very universal documentation problem, regardless of what platform it&amp;#x27;s targeting.&lt;p&gt;I have done the same with React - but it gets messy. Something nice like in the post would be great for that.&lt;p&gt;Too often I see very poor Storybook sites in the wild (a web based design system visual explorer, somewhat like the screenshot in the post) where no thought was given to this exact problem.&lt;p&gt;Instead of something meaningful like in the post, I see:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    () =&amp;gt; &amp;lt;TextInputStorybook &amp;#x2F;&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
As the only avaliable code. The point of the code blocks is so people can copy paste. When I see that, I know I&amp;#x27;m in for a rough ride because the code quality inevitably isn&amp;#x27;t any good either.&lt;p&gt;For reference, this is easily the best design system I know of: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;seek-oss.github.io&amp;#x2F;braid-design-system&amp;#x2F;components&amp;#x2F;Text&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;seek-oss.github.io&amp;#x2F;braid-design-system&amp;#x2F;components&amp;#x2F;Te...&lt;/a&gt; I use this as a reference when I work on my own.</text></comment>
<story><title>Clojure macros continue to surprise me</title><url>https://tonsky.me/blog/clojure-macros/</url></story><parent_chain></parent_chain><comment><author>seancorfield</author><text>The fifth time this has been posted in just over a week... it must be a REALLY good article! :)</text></comment>