<?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: Horses for courses</title>
	<atom:link href="http://blog.markturansky.com/archives/12/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.markturansky.com/archives/12</link>
	<description>software architecture &#38; engineering, code hints, sometimes philosophy, photography, life, etc.</description>
	<lastBuildDate>Thu, 19 Jan 2012 14:26:50 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Christian Posta</title>
		<link>http://blog.markturansky.com/archives/12/comment-page-1#comment-1064</link>
		<dc:creator>Christian Posta</dc:creator>
		<pubDate>Tue, 26 May 2009 14:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.markturansky.com/?p=12#comment-1064</guid>
		<description>I too would be interested in seeing the Java version :)</description>
		<content:encoded><![CDATA[<p>I too would be interested in seeing the Java version <img src='http://blog.markturansky.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Topnotch</title>
		<link>http://blog.markturansky.com/archives/12/comment-page-1#comment-1040</link>
		<dc:creator>Topnotch</dc:creator>
		<pubDate>Mon, 18 May 2009 20:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.markturansky.com/?p=12#comment-1040</guid>
		<description>Could you add the Java program you wrote for comparison so others can judge on the differences needed between completing this task between Java and Python?</description>
		<content:encoded><![CDATA[<p>Could you add the Java program you wrote for comparison so others can judge on the differences needed between completing this task between Java and Python?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan</title>
		<link>http://blog.markturansky.com/archives/12/comment-page-1#comment-1039</link>
		<dc:creator>Ivan</dc:creator>
		<pubDate>Mon, 18 May 2009 19:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.markturansky.com/?p=12#comment-1039</guid>
		<description>&quot;Right tool for the job&quot; usually means &quot;my subjective criteria for success&quot;.</description>
		<content:encoded><![CDATA[<p>&#8220;Right tool for the job&#8221; usually means &#8220;my subjective criteria for success&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason McDonald</title>
		<link>http://blog.markturansky.com/archives/12/comment-page-1#comment-2</link>
		<dc:creator>Jason McDonald</dc:creator>
		<pubDate>Mon, 10 Dec 2007 13:52:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.markturansky.com/?p=12#comment-2</guid>
		<description>I never knew you were an equestrian...

I will take credit for the dislike of the term &quot;right tool for the right job&quot;, however dislike of the term is where it ends. Mark is correct in his explanation of using the right horse for the course - the bitter taste from the phrase simply comes from too many people using it too many times as an excuse. 

There are many times in my career I have heard people say &quot;its the right tool for the job&quot; simply because:

1. They were too lazy to research other tools.

2. They were too new/ignorant to understand the full use case for the tool/code/app in question.

3. It was a cool technology  and they just wanted to use it.

Because of the above reasons this term has quickly become cliche and is often offered up as an excuse by those that fall into one of the above categories.

Simply put, the right tool for the right job is a good credo and is well worth following. But with all things, when it becomes a mainstream term it often becomes diluted and loses much of its core meaning.</description>
		<content:encoded><![CDATA[<p>I never knew you were an equestrian&#8230;</p>
<p>I will take credit for the dislike of the term &#8220;right tool for the right job&#8221;, however dislike of the term is where it ends. Mark is correct in his explanation of using the right horse for the course &#8211; the bitter taste from the phrase simply comes from too many people using it too many times as an excuse. </p>
<p>There are many times in my career I have heard people say &#8220;its the right tool for the job&#8221; simply because:</p>
<p>1. They were too lazy to research other tools.</p>
<p>2. They were too new/ignorant to understand the full use case for the tool/code/app in question.</p>
<p>3. It was a cool technology  and they just wanted to use it.</p>
<p>Because of the above reasons this term has quickly become cliche and is often offered up as an excuse by those that fall into one of the above categories.</p>
<p>Simply put, the right tool for the right job is a good credo and is well worth following. But with all things, when it becomes a mainstream term it often becomes diluted and loses much of its core meaning.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

