<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Clojure on Noetic Nought</title>
    <link>https://punchagan.muse-amuse.in/tags/clojure/</link>
    <description>Recent content in Clojure on Noetic Nought</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <copyright>© 2006-2026 CC-BY-SA-4.0</copyright>
    <lastBuildDate>Wed, 22 Nov 2017 10:18:00 +0530</lastBuildDate>
    <atom:link href="https://punchagan.muse-amuse.in/tags/clojure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Preview: A visualization git repository viewer</title>
      <link>https://punchagan.muse-amuse.in/blog/preview-a-visualization-git-repository-viewer/</link>
      <pubDate>Wed, 22 Nov 2017 10:18:00 +0530</pubDate>
      <guid>https://punchagan.muse-amuse.in/blog/preview-a-visualization-git-repository-viewer/</guid>
      <description>&lt;p&gt;A few weeks ago, I was watching a talk title &lt;a href=&#34;https://www.youtube.com/watch?v=fThhbt23SGM&#34;&gt;Design is a Search Problem&lt;/a&gt; by&#xA;&lt;a href=&#34;https://twitter.com/mbostock&#34;&gt;@mbostock&lt;/a&gt; of d3 fame, which he gave a couple of years ago while he was still&#xA;working at the New York Times.&lt;/p&gt;&#xA;&lt;p&gt;Primarily, he&amp;rsquo;s trying to drive home the point that the process of coming up&#xA;with a good design (for a data visualization) is a hard problem &amp;ndash; there are a&#xA;few thumb rules and philosophical guidelines on how to come up with one, but&#xA;there are no silver bullets to come up with a good design for every scenario.&lt;/p&gt;&#xA;&lt;p&gt;He makes the case for a process that lets you efficiently try out a lot of&#xA;designs to see what works and what doesn&amp;rsquo;t. In the latter part of his talk he&#xA;goes on to demo an internal tool at NYT called Preview, that they use view,&#xA;explore and contribute to each others&amp;rsquo; work. I hoped that in the two years since&#xA;the talk was given, this tool would&amp;rsquo;ve been open-sourced, but it was not to be.&lt;/p&gt;&#xA;&lt;p&gt;So, I started working on my own project, also called &lt;a href=&#34;https://github.com/punchagan/preview&#34;&gt;Preview&lt;/a&gt;, that has a similar&#xA;set of features to those described in the talk. Even if I am not working in a&#xA;visualization team, I think it would be pretty useful to have such a tool to&#xA;explore the work of other people to learn more about their process, when coming&#xA;up with a visualization/design.&lt;/p&gt;&#xA;&lt;p&gt;Currently, Preview lets you keep track of all the repositories of a single&#xA;user/organisation on GitHub. Any repository with an &lt;code&gt;index.html&lt;/code&gt; file is assumed&#xA;to be a repository of interest, and tracked.&lt;/p&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://punchagan.muse-amuse.in/ox-hugo/repo-listing.png&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;It also lets you view the screenshots for a repository over all the commits in&#xA;the repository. This is intended to be some sort of a visual version of git log.&lt;/p&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://punchagan.muse-amuse.in/ox-hugo/screenshots-delhi-traffic-story.png&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;You can also view any repository at the latest commit on any branch.&lt;/p&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://punchagan.muse-amuse.in/ox-hugo/preview-branches.png&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;The tool is pretty new and quite brittle right now, but already quite functional&#xA;and useful, I think. If you do give it a spin, I&amp;rsquo;d love to hear your comments&#xA;and feedback.&lt;/p&gt;&#xA;</description>
    </item>
  </channel>
</rss>
