<?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: Personal victories</title>
	<atom:link href="http://edendevelopment.co.uk/blogs/company/2008/11/21/personal-victories/feed/" rel="self" type="application/rss+xml" />
	<link>http://edendevelopment.co.uk/blogs/company/2008/11/21/personal-victories/</link>
	<description>Eden Development Company Blog</description>
	<lastBuildDate>Tue, 02 Mar 2010 19:27:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Aimee</title>
		<link>http://edendevelopment.co.uk/blogs/company/2008/11/21/personal-victories/comment-page-1/#comment-19</link>
		<dc:creator>Aimee</dc:creator>
		<pubDate>Mon, 08 Dec 2008 13:31:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.edendevelopment.co.uk/blog/?p=48#comment-19</guid>
		<description>Yes, there is still a case for &#039;clarity over cleverness&#039;. You could write an amazing one-liner that&#039;s really fast and impressive, but nobody can understand actually what it does. I must remain vigilant not to fall into that trap.

Another potential trap of refactoring is what i call the &#039;treasure trail&#039;. You break everything down into tiny little functions which call other functions, often in different files. It can be quite a hunt to find the piece of code you&#039;re looking for.</description>
		<content:encoded><![CDATA[<p>Yes, there is still a case for &#8216;clarity over cleverness&#8217;. You could write an amazing one-liner that&#8217;s really fast and impressive, but nobody can understand actually what it does. I must remain vigilant not to fall into that trap.</p>
<p>Another potential trap of refactoring is what i call the &#8216;treasure trail&#8217;. You break everything down into tiny little functions which call other functions, often in different files. It can be quite a hunt to find the piece of code you&#8217;re looking for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://edendevelopment.co.uk/blogs/company/2008/11/21/personal-victories/comment-page-1/#comment-17</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Fri, 05 Dec 2008 11:45:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.edendevelopment.co.uk/blog/?p=48#comment-17</guid>
		<description>Thats the really cool thing that I have learnt from Ruby. If the code looks messy or there is a lot of repetition then there is usually a much shorter way of writing it. However I do find that sometimes cutting it down a lot can sometimes make its purpose or function less obvious (not in this case), or is that just me?</description>
		<content:encoded><![CDATA[<p>Thats the really cool thing that I have learnt from Ruby. If the code looks messy or there is a lot of repetition then there is usually a much shorter way of writing it. However I do find that sometimes cutting it down a lot can sometimes make its purpose or function less obvious (not in this case), or is that just me?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
