<?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>Strong as an Ox &#187; agile</title>
	<atom:link href="http://www.strongasanox.co.uk/tag/agile/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.strongasanox.co.uk</link>
	<description>Ian Oxley - ASP.NET, PHP, JavaScript and Web Applications</description>
	<lastBuildDate>Tue, 24 Aug 2010 22:54:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Google, BigTable and YAGNI</title>
		<link>http://www.strongasanox.co.uk/2008/08/11/google-bigtable-and-yagni/</link>
		<comments>http://www.strongasanox.co.uk/2008/08/11/google-bigtable-and-yagni/#comments</comments>
		<pubDate>Mon, 11 Aug 2008 20:27:09 +0000</pubDate>
		<dc:creator>Ian</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[google]]></category>

		<guid isPermaLink="false">http://ianoxley.wordpress.com/?p=29</guid>
		<description><![CDATA[YAGNI &#8211; short for &#8220;You Aren&#8217;t Going to Need It&#8221; &#8211; is the acronym given to not writing code until you are sure you are actually going to need it. While reading Google&#8217;s paper on BigTable the other day it was interesting to read that this was one of the lessons learned during its development: [...]]]></description>
			<content:encoded><![CDATA[<p><a title="You Aren't Going to Need It" href="http://en.wikipedia.org/wiki/You_Ain%27t_Gonna_Need_It">YAGNI</a> &#8211; short for &#8220;You Aren&#8217;t Going to Need It&#8221; &#8211; is the acronym given to not writing code until you are sure you are actually going to need it. While reading Google&#8217;s paper on BigTable the other day it was interesting to read that this was one of the lessons learned during its development:</p>
<blockquote cite="http://labs.google.com/papers/bigtable-osdi06.pdf"><p>Another lesson we learned is that it is important to delay adding new features until it is clear how the new features will be used. For example, we initially planned to support general-purpose transactions in our API. Because we did not have an immediate use for them, however,<br />
we did not implement them.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.strongasanox.co.uk/2008/08/11/google-bigtable-and-yagni/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
