<?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: Don&#8217;t Make Me Think</title>
	<atom:link href="http://addictedtonew.com/archives/156/dont-make-me-think/feed/" rel="self" type="application/rss+xml" />
	<link>http://addictedtonew.com/archives/156/dont-make-me-think/</link>
	<description>John Nunemaker\'s thoughts and such</description>
	<lastBuildDate>Sun, 01 Nov 2009 17:19:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Nunemaker</title>
		<link>http://addictedtonew.com/archives/156/dont-make-me-think/comment-page-1/#comment-3123</link>
		<dc:creator>John Nunemaker</dc:creator>
		<pubDate>Tue, 13 Jun 2006 04:39:31 +0000</pubDate>
		<guid isPermaLink="false">http://addictedtonew.com/archives/156/dont-make-me-think/#comment-3123</guid>
		<description>Well, the &#039;&#039; is a leftover from PHP and I was just showing a wrong way to do it. That is a good point though as I should have used the more Rubyesque nil than single quotes. 

As to the obviousness of writing easy to use code, I don&#039;t believe it is obvious. If it was obvious, all developers would code this way. I&#039;ve downloaded a few RubyForge projects that accept multiple parameters instead of a Hash. That is actually what prompted me to write this article.</description>
		<content:encoded><![CDATA[<p>Well, the &#8221; is a leftover from PHP and I was just showing a wrong way to do it. That is a good point though as I should have used the more Rubyesque nil than single quotes. </p>
<p>As to the obviousness of writing easy to use code, I don&#8217;t believe it is obvious. If it was obvious, all developers would code this way. I&#8217;ve downloaded a few RubyForge projects that accept multiple parameters instead of a Hash. That is actually what prompted me to write this article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dag Odenhall</title>
		<link>http://addictedtonew.com/archives/156/dont-make-me-think/comment-page-1/#comment-3119</link>
		<dc:creator>Dag Odenhall</dc:creator>
		<pubDate>Tue, 13 Jun 2006 02:27:24 +0000</pubDate>
		<guid isPermaLink="false">http://addictedtonew.com/archives/156/dont-make-me-think/#comment-3119</guid>
		<description>Isn&#039;t this obvious? I use it in any method with either many arguments, or one where many are optional etcetera. Oh, and use &quot;nil&quot; rather than &#039;&#039; :)</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t this obvious? I use it in any method with either many arguments, or one where many are optional etcetera. Oh, and use &#8220;nil&#8221; rather than &#8221; :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabe</title>
		<link>http://addictedtonew.com/archives/156/dont-make-me-think/comment-page-1/#comment-3050</link>
		<dc:creator>Gabe</dc:creator>
		<pubDate>Sun, 11 Jun 2006 19:22:20 +0000</pubDate>
		<guid isPermaLink="false">http://addictedtonew.com/archives/156/dont-make-me-think/#comment-3050</guid>
		<description>I first was introduced to named parameters when I looked into Objective-C for Cocoa programming.  The Ruby way of accepting a hash as a final parameter strikes me as a worthwhile bit of magic (I&#039;m generally against magic, which is why I don&#039;t like Perl).  Named parameters are definitely worth the verbosity.</description>
		<content:encoded><![CDATA[<p>I first was introduced to named parameters when I looked into Objective-C for Cocoa programming.  The Ruby way of accepting a hash as a final parameter strikes me as a worthwhile bit of magic (I&#8217;m generally against magic, which is why I don&#8217;t like Perl).  Named parameters are definitely worth the verbosity.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

