<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>stone mind</title>
	<atom:link href="http://www.stonemind.net/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stonemind.net/blog</link>
	<description></description>
	<pubDate>Fri, 08 Aug 2008 17:28:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
	<language>en</language>
			<item>
		<title>Further Impressions of the Blueprint CSS Framework</title>
		<link>http://www.stonemind.net/blog/2008/08/08/further-impressions-of-the-blueprint-css-framework/</link>
		<comments>http://www.stonemind.net/blog/2008/08/08/further-impressions-of-the-blueprint-css-framework/#comments</comments>
		<pubDate>Fri, 08 Aug 2008 17:25:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[talk nerdy to me]]></category>

		<guid isPermaLink="false">http://www.stonemind.net/blog/?p=91</guid>
		<description><![CDATA[Much to my surprise, one of my most popular blog posts has been <a href="http://www.stonemind.net/blog/2007/08/25/first-impressions-of-the-blueprint-css-framework/">First Impressions of the Blueprint CSS Framework</a>. People continue to read it, cite it, and comment on it, even though it is horribly out of date.

The post was written a year ago using the 0.40 version of Blueprint, which is currently at 0.7.1 as this is being written. And I wrote this post as sort of a test, and didn't intend it to be a Blueprint tutorial in anyway. I am not a CSS guru, which I thought might make my experiences with Blueprint more interesting, as someone who might particularly benefit from this framework.

Given that this post continues to be cited, however, I feel that I'm doing a disservice to the Blueprint project. So, I want to try to set the record straight in this post.]]></description>
		<wfw:commentRss>http://www.stonemind.net/blog/2008/08/08/further-impressions-of-the-blueprint-css-framework/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The 416</title>
		<link>http://www.stonemind.net/blog/2008/07/18/the-416/</link>
		<comments>http://www.stonemind.net/blog/2008/07/18/the-416/#comments</comments>
		<pubDate>Fri, 18 Jul 2008 18:58:13 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[cultural learnings]]></category>

		<guid isPermaLink="false">http://www.stonemind.net/blog/2008/07/18/the-416/</guid>
		<description><![CDATA[Last night during one of my final email checks of the day, I got an email message from a recruiter. What made this particular email interesting was that the recruiter didn't bother to hide any of the addresses he had sent this email to, and I was able to see just how many people get targeted in these types of emails. In this case, it was 416 (or so I'm told--someone counted). I went to sleep shortly thereafter, and slept in, taking Friday off. When I woke up and finally got around to my first email check of the day, I was puzzled to see a thread in Gmail that was 61 messages long. Some poor schlub had hit reply-to-all on that recruiter's email, and drama followed. People replied-to-all complaining at first, but then the emails quickly turned to seeing the humor in the situation. Then people started to introduce each other...]]></description>
		<wfw:commentRss>http://www.stonemind.net/blog/2008/07/18/the-416/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Misguided Attempts to Develop Overspecialized Skills.</title>
		<link>http://www.stonemind.net/blog/2008/07/03/misguided-attempts-to-develop-overspecialized-skills/</link>
		<comments>http://www.stonemind.net/blog/2008/07/03/misguided-attempts-to-develop-overspecialized-skills/#comments</comments>
		<pubDate>Thu, 03 Jul 2008 15:46:39 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[cultural learnings]]></category>

		<guid isPermaLink="false">http://www.stonemind.net/blog/2008/07/03/misguided-attempts-to-develop-overspecialized-skills/</guid>
		<description><![CDATA[Over the years, I've encountered a number of people trying to specialize too narrowly in their jobs, to the detriment of all involved. Here are a few examples of the behavior I see most often...]]></description>
		<wfw:commentRss>http://www.stonemind.net/blog/2008/07/03/misguided-attempts-to-develop-overspecialized-skills/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Drupal 6 Site Structure Script.</title>
		<link>http://www.stonemind.net/blog/2008/06/23/drupal-6-site-structure-script/</link>
		<comments>http://www.stonemind.net/blog/2008/06/23/drupal-6-site-structure-script/#comments</comments>
		<pubDate>Tue, 24 Jun 2008 01:01:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[talk nerdy to me]]></category>
<category>Drupal</category>
		<guid isPermaLink="false">http://www.stonemind.net/blog/2008/06/23/drupal-6-site-structure-script/</guid>
		<description><![CDATA[I continue to find useful the <a href="http://www.stonemind.net/blog/2007/11/18/a-possible-approach-to-importing-static-content-into-drupal/">script I posted</a> some time ago that creates a basic site structure in Drupal. Its not uncommon that a customer will want a leg up on migrating their content into Drupal, or will have a basic structure in mind even before they fill it with content.

I recently started working in Drupal 6, now that many of the modules I typically use are at least in beta for Drupal 6. So, I found that I needed to update the script as follows:]]></description>
		<wfw:commentRss>http://www.stonemind.net/blog/2008/06/23/drupal-6-site-structure-script/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Drupal Developer&#8217;s Orientation</title>
		<link>http://www.stonemind.net/blog/2008/06/08/drupal-developers-orientation/</link>
		<comments>http://www.stonemind.net/blog/2008/06/08/drupal-developers-orientation/#comments</comments>
		<pubDate>Sun, 08 Jun 2008 21:46:49 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[talk nerdy to me]]></category>
<category>Drupal</category>
		<guid isPermaLink="false">http://www.stonemind.net/blog/2008/06/08/drupal-developers-orientation/</guid>
		<description><![CDATA[I am starting development of a significant new Web site implemented in Drupal, and have as my team five talented, but relatively inexperienced, developers with little existing knowledge of Drupal. This is my attempt to provide a quick orientation to Drupal from a developer's perspective, based on my experience.]]></description>
		<wfw:commentRss>http://www.stonemind.net/blog/2008/06/08/drupal-developers-orientation/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Common open source tools make generating visual software documentation easier.</title>
		<link>http://www.stonemind.net/blog/2008/05/21/common-open-source-tools-make-generating-visual-software-documentation-easier/</link>
		<comments>http://www.stonemind.net/blog/2008/05/21/common-open-source-tools-make-generating-visual-software-documentation-easier/#comments</comments>
		<pubDate>Wed, 21 May 2008 23:36:31 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[talk nerdy to me]]></category>
<category>imagemagick</category><category>shell scripting</category>
		<guid isPermaLink="false">http://www.stonemind.net/blog/2008/05/21/common-open-source-tools-make-generating-visual-software-documentation-easier/</guid>
		<description><![CDATA[Recently, I needed to create end-user documentation for a desktop application. Although screencasting is a possible alternative, I didn't feel it was appropriate in this type of situation, where the end user really needs something printer-friendly to have in hand while using the application.

Although I did want the document to be highly visual, I wasn't looking forward to the tedious process of capturing screens manually, one by one, then inserting them into a document, manually, one by one. I needed something that would streamline both of these processes so I could concentrate on making good documentation.]]></description>
		<wfw:commentRss>http://www.stonemind.net/blog/2008/05/21/common-open-source-tools-make-generating-visual-software-documentation-easier/feed/</wfw:commentRss>
		</item>
		<item>
		<title>ZoomifyImage Version 1.4 Released Today.</title>
		<link>http://www.stonemind.net/blog/2008/05/14/zoomifyimage-version-14-released-today/</link>
		<comments>http://www.stonemind.net/blog/2008/05/14/zoomifyimage-version-14-released-today/#comments</comments>
		<pubDate>Wed, 14 May 2008 19:58:05 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[talk nerdy to me]]></category>
<category>Python</category><category>Zope</category>
		<guid isPermaLink="false">http://www.stonemind.net/blog/2008/05/14/zoomifyimage-version-14-released-today/</guid>
		<description><![CDATA[It seems I make a new release of ZoomifyImage once a year like clockwork. This time around, I fixed a minor bug and made a few enhancements including writing temporary files to the system temporary directory and accounting for changes in ZODB's transaction handling. ]]></description>
		<wfw:commentRss>http://www.stonemind.net/blog/2008/05/14/zoomifyimage-version-14-released-today/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Fixing Shipcalc Module Bug is an Example of Overriding Drupal Forms.</title>
		<link>http://www.stonemind.net/blog/2008/04/23/fixing-shipcalc-module-bug-is-an-example-of-overriding-drupal-forms/</link>
		<comments>http://www.stonemind.net/blog/2008/04/23/fixing-shipcalc-module-bug-is-an-example-of-overriding-drupal-forms/#comments</comments>
		<pubDate>Wed, 23 Apr 2008 14:42:52 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[talk nerdy to me]]></category>
<category>Drupal</category><category>ecommerce</category>
		<guid isPermaLink="false">http://www.stonemind.net/blog/2008/04/23/fixing-shipcalc-module-bug-is-an-example-of-overriding-drupal-forms/</guid>
		<description><![CDATA[A customer on a newly launched Drupal e-commerce site I produced reported the following error:

<blockquote>
Please enter a valid ZIP Code for the sender. (error -2147219498) usps configuration error. Please notify the site administrator.
</blockquote>

Which occurred during the checkout process and only happened when a zip code contained a "+ 4" code at the end.

Of course, I often find Google to be the best debugging tool of all, and I quickly found <a href="http://drupal.org/node/81914">this post</a> containing a workaround by Kenneth Bartlett that not only made it so I didn't have to untangle the shipcalc module's code, which would likely mean debugging Web Services calls to USPS, but is actually a pretty good solution in its own right I think.

The only thing I didn't like about it was that it directly patched an e-commerce module file at modules/ecommerce/address/address.module. Whenever I use a piece of customizable software like Drupal (or Wordpress, osCommerce, etc.) I avoid directly patching both the core code and any third party modules, because this creates a maintenance burden for me when I want to upgrade the core software or an affected module, which could potentially wipe out these kinds of patches. I have my hands maintaining my own code, I don't want to worry about modules I didn't write.]]></description>
		<wfw:commentRss>http://www.stonemind.net/blog/2008/04/23/fixing-shipcalc-module-bug-is-an-example-of-overriding-drupal-forms/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Being Steve Jobs.</title>
		<link>http://www.stonemind.net/blog/2008/04/17/being-steve-jobs/</link>
		<comments>http://www.stonemind.net/blog/2008/04/17/being-steve-jobs/#comments</comments>
		<pubDate>Fri, 18 Apr 2008 00:48:25 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[cultural learnings]]></category>

		<guid isPermaLink="false">http://www.stonemind.net/blog/2008/04/17/being-steve-jobs/</guid>
		<description><![CDATA[I am reading <em>The Second Coming of Steve Jobs </em>by Alan Deutschman, and although the book was published way back in 2000, it was written at a time when Apple had already made a strong comeback, so I thought that it would still be a relevant case study of Job's and Apple's success.]]></description>
		<wfw:commentRss>http://www.stonemind.net/blog/2008/04/17/being-steve-jobs/feed/</wfw:commentRss>
		</item>
		<item>
		<title>A Potential Confusion When Converting HABTM Relationships to has_many :through.</title>
		<link>http://www.stonemind.net/blog/2008/04/10/a-potential-confusion-when-converting-habtm-relationships-to-has_many-through/</link>
		<comments>http://www.stonemind.net/blog/2008/04/10/a-potential-confusion-when-converting-habtm-relationships-to-has_many-through/#comments</comments>
		<pubDate>Thu, 10 Apr 2008 19:59:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[talk nerdy to me]]></category>
<category>Ruby on Rails</category>
		<guid isPermaLink="false">http://www.stonemind.net/blog/2008/04/10/a-potential-confusion-when-converting-habtm-relationships-to-has_many-through/</guid>
		<description><![CDATA[As someone relatively new to Ruby on Rails, I managed to confuse myself on one of my Rails projects recently when I decided to follow some very logical advice in Obie Fernandez's <em>The Rails Way</em> that said that has_and_belongs_to_many (habtm) relationships were essentially deprecated in Rails, and that has_many :through was the preferred way to handle many-to-many relationships. 

With has_many :through, the join table becomes a full-fledged rails model, meaning that you have more flexibility to extend the functionality of that model as your application evolves in the future--a very sensible best practice. So, I decided to convert an existing relationship that I had specified as habtm to has_many :through. I began to see errors that initially confused me, along the lines of <i>NameError: Uninitialized Constant ...</i>. I had misnamed my join model and table because I was still thinking from the habtm perspective instead of treating the new model as I would any other model in a has_many...belongs_to relationship.]]></description>
		<wfw:commentRss>http://www.stonemind.net/blog/2008/04/10/a-potential-confusion-when-converting-habtm-relationships-to-has_many-through/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
