<?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: Clean Code: Book Review</title>
	<atom:link href="http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Sat, 11 Feb 2012 23:17:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark Needham: Coding: Write the first one ugly &#124; Software Secret Weapons</title>
		<link>http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/comment-page-1/#comment-52926</link>
		<dc:creator>Mark Needham: Coding: Write the first one ugly &#124; Software Secret Weapons</dc:creator>
		<pubDate>Sun, 03 Oct 2010 18:53:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=323#comment-52926</guid>
		<description>[...] think this is a really good piece of advice and it seems along the same lines as a suggestion from Uncle Bob in Clean Code:  When I write functions they come out long and complicatedâ¦then I massage and refine that [...]</description>
		<content:encoded><![CDATA[<p>[...] think this is a really good piece of advice and it seems along the same lines as a suggestion from Uncle Bob in Clean Code:  When I write functions they come out long and complicatedâ¦then I massage and refine that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coding: Write the first one ugly at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/comment-page-1/#comment-52730</link>
		<dc:creator>Coding: Write the first one ugly at Mark Needham</dc:creator>
		<pubDate>Sun, 03 Oct 2010 05:04:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=323#comment-52730</guid>
		<description>[...] think this is a really good piece of advice and it seems along the same lines as a suggestion from Uncle Bob in Clean Code:  When I write functions they come out long and complicated…then I massage and refine that code, [...]</description>
		<content:encoded><![CDATA[<p>[...] think this is a really good piece of advice and it seems along the same lines as a suggestion from Uncle Bob in Clean Code:  When I write functions they come out long and complicated…then I massage and refine that code, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Book Club: SOLID Principles (Uncle Bob Martin) at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/comment-page-1/#comment-22599</link>
		<dc:creator>Book Club: SOLID Principles (Uncle Bob Martin) at Mark Needham</dc:creator>
		<pubDate>Tue, 15 Sep 2009 15:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=323#comment-22599</guid>
		<description>[...] quite like the newspaper metaphor to writing code which Uncle Bob describes in Clean Code and he elabroates on this further in a recent post about extracting method until you drop. I find [...]</description>
		<content:encoded><![CDATA[<p>[...] quite like the newspaper metaphor to writing code which Uncle Bob describes in Clean Code and he elabroates on this further in a recent post about extracting method until you drop. I find [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coding: Single Level of Abstraction Principle at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/comment-page-1/#comment-18533</link>
		<dc:creator>Coding: Single Level of Abstraction Principle at Mark Needham</dc:creator>
		<pubDate>Fri, 12 Jun 2009 07:37:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=323#comment-18533</guid>
		<description>[...] first came across the idea of writing code at the same level of abstraction in Uncle Bob&#039;s Clean Code although I only learnt about the actual term in Neal Ford&#039;s The Productive [...]</description>
		<content:encoded><![CDATA[<p>[...] first came across the idea of writing code at the same level of abstraction in Uncle Bob&#8217;s Clean Code although I only learnt about the actual term in Neal Ford&#8217;s The Productive [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coding: Why do we extract method? at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/comment-page-1/#comment-18286</link>
		<dc:creator>Coding: Why do we extract method? at Mark Needham</dc:creator>
		<pubDate>Thu, 04 Jun 2009 10:34:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=323#comment-18286</guid>
		<description>[...] since I&#039;ve read Uncle Bob&#039;s Clean Code book my approach to coding has been all about the &#039;extract method&#039; refactoring - I pretty much look to [...]</description>
		<content:encoded><![CDATA[<p>[...] since I&#8217;ve read Uncle Bob&#8217;s Clean Code book my approach to coding has been all about the &#8216;extract method&#8217; refactoring &#8211; I pretty much look to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pair Programming: Refactoring at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/comment-page-1/#comment-17675</link>
		<dc:creator>Pair Programming: Refactoring at Mark Needham</dc:creator>
		<pubDate>Tue, 26 May 2009 13:50:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=323#comment-17675</guid>
		<description>[...] there are certainly books which explain how to do refactorings on our code a lot of the approaches that I like to use have [...]</description>
		<content:encoded><![CDATA[<p>[...] there are certainly books which explain how to do refactorings on our code a lot of the approaches that I like to use have [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Finding the value in fixing technical debt at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/comment-page-1/#comment-2645</link>
		<dc:creator>Finding the value in fixing technical debt at Mark Needham</dc:creator>
		<pubDate>Sat, 10 Jan 2009 04:07:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=323#comment-2645</guid>
		<description>[...] reading Uncle Bob&#039;s Clean Code I&#039;ve become a bit fanatical in my approach to trying to make code as readable as possible, mainly [...]</description>
		<content:encoded><![CDATA[<p>[...] reading Uncle Bob&#8217;s Clean Code I&#8217;ve become a bit fanatical in my approach to trying to make code as readable as possible, mainly [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corey Haines</title>
		<link>http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/comment-page-1/#comment-2489</link>
		<dc:creator>Corey Haines</dc:creator>
		<pubDate>Sun, 04 Jan 2009 14:39:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=323#comment-2489</guid>
		<description>&quot;I also found the following statement revealing as I was under the assumption that experienced developers wrote code like this first time&quot;

That is an interesting assumption; I wonder if others have it. I&#039;ve often thought it would be a neat application to look through your scm repo for a file and watch the evolution of a file/your system&#039;s code structure over time. I commit constantly (every time you commit, and angel gets it wings), so there is a lot of crappy, ugly code stored in my repo throughout the process.

I&#039;m even willing to leave some not-so-pretty code sitting around, as long as it passes the specs, if I can&#039;t seem to see my way out of it at the moment. I&#039;ll then either figure it out later, or I&#039;ll show it to someone new, and they usually will have an idea.</description>
		<content:encoded><![CDATA[<p>&#8220;I also found the following statement revealing as I was under the assumption that experienced developers wrote code like this first time&#8221;</p>
<p>That is an interesting assumption; I wonder if others have it. I&#8217;ve often thought it would be a neat application to look through your scm repo for a file and watch the evolution of a file/your system&#8217;s code structure over time. I commit constantly (every time you commit, and angel gets it wings), so there is a lot of crappy, ugly code stored in my repo throughout the process.</p>
<p>I&#8217;m even willing to leave some not-so-pretty code sitting around, as long as it passes the specs, if I can&#8217;t seem to see my way out of it at the moment. I&#8217;ll then either figure it out later, or I&#8217;ll show it to someone new, and they usually will have an idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What is a unit test? at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/comment-page-1/#comment-688</link>
		<dc:creator>What is a unit test? at Mark Needham</dc:creator>
		<pubDate>Fri, 10 Oct 2008 13:24:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=323#comment-688</guid>
		<description>[...] make the former happen but the final word goes to Uncle Bob who suggests the F.I.R.S.T acronym in Clean Code to describe what well written (clean) unit tests should look [...]</description>
		<content:encoded><![CDATA[<p>[...] make the former happen but the final word goes to Uncle Bob who suggests the F.I.R.S.T acronym in Clean Code to describe what well written (clean) unit tests should look [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Test Driven Development By Example: Book Review at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/comment-page-1/#comment-637</link>
		<dc:creator>Test Driven Development By Example: Book Review at Mark Needham</dc:creator>
		<pubDate>Tue, 07 Oct 2008 13:20:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=323#comment-637</guid>
		<description>[...] How closely will the lessons here link to those from Clean Code? [...]</description>
		<content:encoded><![CDATA[<p>[...] How closely will the lessons here link to those from Clean Code? [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

