<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>let x=x &#187; no best practice</title>
	<atom:link href="http://www.crazymcphee.net/x/tag/no-best-practice/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.crazymcphee.net/x</link>
	<description>programming idiom and methodology</description>
	<lastBuildDate>Fri, 27 Jan 2012 09:36:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>&#8220;Best practice&#8221; considered harmful</title>
		<link>http://www.crazymcphee.net/x/2009/02/01/best-practice-considered-harmful/</link>
		<comments>http://www.crazymcphee.net/x/2009/02/01/best-practice-considered-harmful/#comments</comments>
		<pubDate>Sun, 01 Feb 2009 07:00:11 +0000</pubDate>
		<dc:creator>Scot Mcphee</dc:creator>
				<category><![CDATA[professional practice]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[methodology]]></category>
		<category><![CDATA[no best practice]]></category>
		<category><![CDATA[profession]]></category>

		<guid isPermaLink="false">http://www.crazymcphee.net/x/?p=130</guid>
		<description><![CDATA[Oh yes boys and girls, despite what the &#8220;Project Management Manifesto&#8221; (and plenty of others) might like to say &#8211; &#8216;Best Practice&#8217; is actually harmful. It is nearly always a codeword for kind of lazy thinking looking to apply a template from someplace else, and is inimical to actual excellence. While experience will give you [...]]]></description>
			<content:encoded><![CDATA[<p>Oh yes boys and girls, despite what the &#8220;<a href="http://pmmanifesto.ning.com/" target="_blank">Project Management Manifesto</a>&#8221; (and <a title="agile 'best practices' search on google" href="http://www.google.com.au/search?hl=en&amp;q=agile+%22best+practices%22" target="_blank">plenty of others</a>) might like to say &#8211; &#8216;Best Practice&#8217; is <a href="http://www.satisfice.com/blog/archives/27" target="_blank">actually harmful</a>. It is nearly always a codeword for kind of lazy thinking looking to apply a template from someplace else, and is inimical to actual <em>excellence</em>. While experience will give you ideas for what might or might not work, it&#8217;s a big mistake to take yesterday&#8217;s solution and <a title="Estimate Goat" href="http://estimategoat.com/" target="_blank">cookie-cutter</a> it to today&#8217;s problem. In software development, <a href="http://www.ambysoft.com/essays/bestPractices.html" target="_blank">context is king</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.crazymcphee.net/x/2009/02/01/best-practice-considered-harmful/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

