<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>8th Light Blog: Something new, every day</title>
    <link>http://blog.8thlight.com/articles/2007/06/26/something-new-every-day</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>In the minds of the craftsmen...</description>
    <item>
      <title>Something new, every day</title>
      <description>&lt;p&gt;Last December I went to to StarEast in Orlando because my fiancee is a tester and I well, I like sun.  While there I picked up the book &lt;a href="http://www.pragmaticprogrammer.com/titles/pad/"&gt;Practices of an Agile Developer&lt;/a&gt; and was particularly struck by the practice to keep a &amp;#8220;Solutions Log.&amp;#8221;  The way a solutions log works is simple.  Every time you find a solution to a problem you write it down, and later when you are confronted by a similar problem you have a reference.  &amp;#8220;Gee Whiz what a great idea!&amp;#8221; I thought to myself, because I think to myself like Beaver Cleaver, &amp;#8220;this way when Jim asks me about that bug I solved two weeks ago, I&amp;#8217;ll know &lt;em&gt;exactly&lt;/em&gt; what to tell him, instead of saying &amp;#8220;uhhh, err, yeah I sorta kinda remember&amp;#8230;&amp;#8221;  It really was an amazing revelation, seeing as how I hadn&amp;#8217;t met Jim yet.&lt;/p&gt;

&lt;p&gt;&lt;img src="http://blog.8thlight.com/files/2007-06-21_genius_hat.jpg" alt="genius_hat" title="" style="float:left"/&gt;
Then I got home and subscribed to &lt;a href="http://www.agiledeveloper.com/blog/PermaLink.aspx?guid=d2754a12-8f7c-4406-a4ad-92dca4c6942d"&gt;Venkat&amp;#8217;s blog&lt;/a&gt; where he recommended &lt;a href="http://www.tiddlywiki.com/"&gt;TiddlyWiki&lt;/a&gt; for keeping this list.  If you&amp;#8217;re unfamiliar with TiddlyWiki it&amp;#8217;s an extremely cool browser-based personal note-taking tool that works entirely via JavaScript and CSS.  You fire up your personal version of the html file, double click, and viola! there you have a note saved into the very document.  Best of all it&amp;#8217;s searchable even via regular expressions and plain text.  With this tool I was gonna be a solution mastermind!  People will ask me for that bug I fixed 14 years ago and I&amp;#8217;ll be right there with my genius hat on and everything.  You do have a genius hat don&amp;#8217;t you?&lt;/p&gt;

&lt;p&gt;&lt;img id="dunce_cap" src="http://blog.8thlight.com/files/2007-06-21_dunce_cap.jpg" alt="dunce_cap" title="" style="float:right"/&gt;
How did it work out?  Roughly 18 months later I have a whopping&amp;#8230; 16 solutions, most of them written in the first week.  You know what I learned from this?  I &lt;em&gt;suck&lt;/em&gt; at keeping a solutions list.  The thing is I have no idea something is a solution to a recurring problem, until I come upon it a second time!  What I need is a way to psychically determine what the solutions I&amp;#8217;m going to need in the future are, and identify them.  Um&amp;#8230;.&lt;/p&gt;

&lt;p&gt;I&amp;#8217;ve decided on a different option, which I think fits in well with the craftsmanship approach of perpetual learning.  Since joining 8th Light I&amp;#8217;ve been lucky enough to learn enormous amounts in a short amount of time, with more on the way, but of course none of this is in my solutions list.  So instead of catching the realization that something is a solution,  I&amp;#8217;m going to write it all down.  I&amp;#8217;ve created a new list, and instead of calling it a Solutions List, it&amp;#8217;s my LearnANewThingEveryDay list.  Every day I&amp;#8217;m obligated to write a new note with something I&amp;#8217;d learned that day.  If a day goes by and I haven&amp;#8217;t learned something, I have to go learn something.   I&amp;#8217;ll read a book, find a great blog posting, try out a coding exercise, whatever.  For example today I have written down some things I didn&amp;#8217;t know about routing in rails.  Mundane stuff that people more experienced with routing already new such as the :path_prefix parameter.  What would be an otherwise fruitless day debugging now has a few little things I&amp;#8217;ve learned from it.  Will I ever search for that item?  I don&amp;#8217;t know - but the point is I can, so when Jim asks me how to get eric/is/the/coolest/blogger in front of all his links, I won&amp;#8217;t stand there scratching my head.  &lt;/p&gt;</description>
      <pubDate>Tue, 26 Jun 2007 05:49:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:3c4907fc-d4d7-4464-b7b6-72c05b22365f</guid>
      <author>Eric</author>
      <link>http://blog.8thlight.com/articles/2007/06/26/something-new-every-day</link>
      <category>Craftsmanship</category>
      <category>Eric</category>
    </item>
  </channel>
</rss>
