<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Developer Timesink: Name Paralysis</title>
	<atom:link href="http://lbrandy.com/blog/2008/08/developer-timesink-name-paralysis/feed/" rel="self" type="application/rss+xml" />
	<link>http://lbrandy.com/blog/2008/08/developer-timesink-name-paralysis/</link>
	<description>{ on programming and the internets, every monday }</description>
	<lastBuildDate>Fri, 03 Feb 2012 14:14:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: lbrandy.com &#187; Blog Archive &#187; Mistakes we made when naming our computers</title>
		<link>http://lbrandy.com/blog/2008/08/developer-timesink-name-paralysis/comment-page-1/#comment-25568</link>
		<dc:creator>lbrandy.com &#187; Blog Archive &#187; Mistakes we made when naming our computers</dc:creator>
		<pubDate>Sun, 27 Sep 2009 21:59:18 +0000</pubDate>
		<guid isPermaLink="false">http://lbrandy.com/blog/?p=43#comment-25568</guid>
		<description>[...] naming theme has a virtually inexhaustible list of easy-to-type (important) names. You can waste a tremendous amount of time finding [...]</description>
		<content:encoded><![CDATA[<p>[...] naming theme has a virtually inexhaustible list of easy-to-type (important) names. You can waste a tremendous amount of time finding [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lbrandy.com &#187; Blog Archive &#187; Setting Goals, Making Money</title>
		<link>http://lbrandy.com/blog/2008/08/developer-timesink-name-paralysis/comment-page-1/#comment-2170</link>
		<dc:creator>lbrandy.com &#187; Blog Archive &#187; Setting Goals, Making Money</dc:creator>
		<pubDate>Mon, 26 Jan 2009 13:07:38 +0000</pubDate>
		<guid isPermaLink="false">http://lbrandy.com/blog/?p=43#comment-2170</guid>
		<description>[...] (the twitterification of a blog)? I&#8217;ll let you decide. Could I make the proggit front page? Turned out to be easy! How about the reddit front page? Done! How about Digg? [...]</description>
		<content:encoded><![CDATA[<p>[...] (the twitterification of a blog)? I&#8217;ll let you decide. Could I make the proggit front page? Turned out to be easy! How about the reddit front page? Done! How about Digg? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: imobi</title>
		<link>http://lbrandy.com/blog/2008/08/developer-timesink-name-paralysis/comment-page-1/#comment-1711</link>
		<dc:creator>imobi</dc:creator>
		<pubDate>Mon, 05 Jan 2009 15:14:19 +0000</pubDate>
		<guid isPermaLink="false">http://lbrandy.com/blog/?p=43#comment-1711</guid>
		<description>&lt;strong&gt;hi...&lt;/strong&gt;

Thank you! I would now go on this blog every day!...</description>
		<content:encoded><![CDATA[<p><strong>hi&#8230;</strong></p>
<p>Thank you! I would now go on this blog every day!&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Jacob</title>
		<link>http://lbrandy.com/blog/2008/08/developer-timesink-name-paralysis/comment-page-1/#comment-36</link>
		<dc:creator>Thomas Jacob</dc:creator>
		<pubDate>Mon, 08 Sep 2008 21:19:12 +0000</pubDate>
		<guid isPermaLink="false">http://lbrandy.com/blog/?p=43#comment-36</guid>
		<description>Great article. I often get caught by name paralysis, and I can hardly move on, then. Usually, it goes away after a while..</description>
		<content:encoded><![CDATA[<p>Great article. I often get caught by name paralysis, and I can hardly move on, then. Usually, it goes away after a while..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://lbrandy.com/blog/2008/08/developer-timesink-name-paralysis/comment-page-1/#comment-35</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Thu, 28 Aug 2008 20:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://lbrandy.com/blog/?p=43#comment-35</guid>
		<description>In my experience, one of the riskiest time for name paralysis is when creating source control repositories for new projects. It&#039;s often very difficult to rename an existing repository (with all the tools I&#039;ve used, at least), so there&#039;s a natural tendency to try to get the name *perfect* the first time. Then you can get stuck before you&#039;ve even started!</description>
		<content:encoded><![CDATA[<p>In my experience, one of the riskiest time for name paralysis is when creating source control repositories for new projects. It&#8217;s often very difficult to rename an existing repository (with all the tools I&#8217;ve used, at least), so there&#8217;s a natural tendency to try to get the name *perfect* the first time. Then you can get stuck before you&#8217;ve even started!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://lbrandy.com/blog/2008/08/developer-timesink-name-paralysis/comment-page-1/#comment-33</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://lbrandy.com/blog/?p=43#comment-33</guid>
		<description>Right now, names do matter. Not just later, but now.

Sure, you can change a name in sed. But that&#039;s missing the problem completely.

The problem is when you have an ambiguous name, different team members develop against their own, sometimes mismatching, ideas of what that name represents. Let&#039;s say I name a variable setView.

To Adam, it means set the current view.

To Bosco, it means a set of views.

To Joe, it means a fixed, static view that cannot be changed.

This example is deliberately contrived to make the problem more obvious. In real life, the names are not as glaringly bad, and the differences in interpretation are more subtle, but they are still there.

Then each developer writes code with their own idea in mind. And when Joe looks at Adam&#039;s code, it kind of makes sense, but seems strange, but Joe brushes it off, wanting to worry about his own stuff. The code diverges and pretty soon you have something sed won&#039;t help with.</description>
		<content:encoded><![CDATA[<p>Right now, names do matter. Not just later, but now.</p>
<p>Sure, you can change a name in sed. But that&#8217;s missing the problem completely.</p>
<p>The problem is when you have an ambiguous name, different team members develop against their own, sometimes mismatching, ideas of what that name represents. Let&#8217;s say I name a variable setView.</p>
<p>To Adam, it means set the current view.</p>
<p>To Bosco, it means a set of views.</p>
<p>To Joe, it means a fixed, static view that cannot be changed.</p>
<p>This example is deliberately contrived to make the problem more obvious. In real life, the names are not as glaringly bad, and the differences in interpretation are more subtle, but they are still there.</p>
<p>Then each developer writes code with their own idea in mind. And when Joe looks at Adam&#8217;s code, it kind of makes sense, but seems strange, but Joe brushes it off, wanting to worry about his own stuff. The code diverges and pretty soon you have something sed won&#8217;t help with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JosefA</title>
		<link>http://lbrandy.com/blog/2008/08/developer-timesink-name-paralysis/comment-page-1/#comment-32</link>
		<dc:creator>JosefA</dc:creator>
		<pubDate>Thu, 28 Aug 2008 12:04:16 +0000</pubDate>
		<guid isPermaLink="false">http://lbrandy.com/blog/?p=43#comment-32</guid>
		<description>No no no no, you&#039;re doing it wrong! http://sancairodicopenhagen.com/joe/five_tips_to_better_variable_naming_practises</description>
		<content:encoded><![CDATA[<p>No no no no, you&#8217;re doing it wrong! <a href="http://sancairodicopenhagen.com/joe/five_tips_to_better_variable_naming_practises" rel="nofollow">http://sancairodicopenhagen.com/joe/five_tips_to_better_variable_naming_practises</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

