<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>It's a .NET Life</title>
	<link>http://www.david-yancey.com/blog</link>
	<description>Thoughts on .NET, Agile and beyond</description>
	<lastBuildDate>Mon, 26 Apr 2010 00:31:18 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.0.1" -->

	<item>
		<title>Throw Away Code (aka Spike Solution)</title>
		<description><![CDATA[  I’ve been talking with a few of my programmers the past few days about the concept of throw away code, asking them if they’ve heard of the concept, or if they’ve thought about implementing it on their teams.   All but one of them replied back to me with variations of “what a waste of [...]]]></description>
		<link>http://www.david-yancey.com/blog/index.php/2009/05/06/throw-away-code-aka-spike-solution/</link>
			</item>
	<item>
		<title>Code Noise Part 2!</title>
		<description><![CDATA[Last time we looked at what Code Noise was.  This time we are going to look at good practices for eliminating code noise. Clean Naming: Clean names reveal intent. Clean names reveal intent. Clean names reveal intent. The point I&#8217;m trying to get across here is that good clean names reveal intent.  So what do [...]]]></description>
		<link>http://www.david-yancey.com/blog/index.php/2009/02/04/code-noise-part-2-2/</link>
			</item>
	<item>
		<title>Code Noise!!!</title>
		<description><![CDATA[If 4 letter words immediately come to mind when you do a code review&#8230;then you might have dirty code. If you wince each time a new feature is requested to be added to your existing library of code&#8230;then you might have dirty code. If the amount of time it takes to research a bug is inversely [...]]]></description>
		<link>http://www.david-yancey.com/blog/index.php/2008/12/10/dirty-code/</link>
			</item>
	<item>
		<title>Refactoring: Getting started is the hard part</title>
		<description><![CDATA[Just the thought of &#8216;refactoring&#8217; can be daunting to a programmer.  Martin Fowler defines &#8216;refactoring&#8217; as: Refactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior. Its heart is a series of small behavior preserving transformations. Each transformation (called a &#8216;refactoring&#8217;) does little, but [...]]]></description>
		<link>http://www.david-yancey.com/blog/index.php/2008/11/25/refactoring-getting-started-is-the-hard-part/</link>
			</item>
	<item>
		<title>Agile and the .NET Community</title>
		<description><![CDATA[Why does it seem that the .NET Community isn&#8217;t very active in the Agile community?  I know that there are Agile practitioners in various .NET shops however, it seems that the overall representation is very minimal.  Is it because of a lack of understanding of the Agile methodologies? Or is there a lack of support [...]]]></description>
		<link>http://www.david-yancey.com/blog/index.php/2008/11/19/agile-and-the-net-community/</link>
			</item>
</channel>
</rss>
