<?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: Availability is a Feature</title>
	<atom:link href="http://www.dancres.org/blitzblog/2007/03/25/availability-is-a-feature/feed/" rel="self" type="application/rss+xml" />
	<link>http://dancres.org/feeder/?FeederAction=clicked&#038;feed=Comments+on+Articles+%28RSS2%29&#038;seed=http%3A%2F%2Fwww.dancres.org%2Fblitzblog%2F2007%2F03%2F25%2Favailability-is-a-feature%2F%23comment-&#038;seed_title=Availability+is+a+Feature</link>
	<description></description>
	<lastBuildDate>Mon, 02 Jan 2012 08:22:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dan Creswell</title>
		<link>http://dancres.org/feeder/?FeederAction=clicked&#038;feed=Comments+on+Articles+%28RSS2%29&#038;seed=http%3A%2F%2Fwww.dancres.org%2Fblitzblog%2F2007%2F03%2F25%2Favailability-is-a-feature%2F%23comment-73&#038;seed_title=Availability+is+a+Feature/comment-page-1/#comment-73</link>
		<dc:creator>Dan Creswell</dc:creator>
		<pubDate>Mon, 26 Mar 2007 05:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.dancres.org/blitzblog/2007/03/25/availability-is-a-feature/#comment-73</guid>
		<description>Hi John,

&quot;Ok I couldn’t help but comment. I view a feature and availability as a classic chicken and egg problem.....&quot;

I think that &quot;make it work, make it maintainable&quot; is acceptable when you start off but particularly in the case of websites I think this bias changes over time.  Once you have a bunch of paying users you want to keep them - availability can have a significant impact on this as has been documented in respect of MySpace.

I&#039;d like to explore this more so let&#039;s consider this example - once I have a database with all the features I require, how much do I value reliability and availability?  Do these things become more or less important as the amount of data (value) in the database grows?  Do these things become more or less important as I gain more dependencies on the database?</description>
		<content:encoded><![CDATA[<p>Hi John,</p>
<p>&#8220;Ok I couldn’t help but comment. I view a feature and availability as a classic chicken and egg problem&#8230;..&#8221;</p>
<p>I think that &#8220;make it work, make it maintainable&#8221; is acceptable when you start off but particularly in the case of websites I think this bias changes over time.  Once you have a bunch of paying users you want to keep them &#8211; availability can have a significant impact on this as has been documented in respect of MySpace.</p>
<p>I&#8217;d like to explore this more so let&#8217;s consider this example &#8211; once I have a database with all the features I require, how much do I value reliability and availability?  Do these things become more or less important as the amount of data (value) in the database grows?  Do these things become more or less important as I gain more dependencies on the database?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://dancres.org/feeder/?FeederAction=clicked&#038;feed=Comments+on+Articles+%28RSS2%29&#038;seed=http%3A%2F%2Fwww.dancres.org%2Fblitzblog%2F2007%2F03%2F25%2Favailability-is-a-feature%2F%23comment-72&#038;seed_title=Availability+is+a+Feature/comment-page-1/#comment-72</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 26 Mar 2007 02:25:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.dancres.org/blitzblog/2007/03/25/availability-is-a-feature/#comment-72</guid>
		<description>Ok I couldn&#039;t help but comment.    I view a feature and availability as a classic chicken and egg problem, but I think the feature always wins.  This profoundly bugs me, because I work on availability, but I&#039;ve rationalized it to this:  Availability can still sell at a &#039;good enough&#039; where good enough can be astonishingly bad.  Features though, don&#039;t seem to have that luxury.  On some level it has to offer something good enough to sell.   My son plays all kinds of online games with his friends that validates this in my mind time and time again.

The first guy that I had that taught me how to develop still resonates with me ... &quot;Make it work,  make it maintainable, make it reliable, make it fast.  Repeat.&quot;</description>
		<content:encoded><![CDATA[<p>Ok I couldn&#8217;t help but comment.    I view a feature and availability as a classic chicken and egg problem, but I think the feature always wins.  This profoundly bugs me, because I work on availability, but I&#8217;ve rationalized it to this:  Availability can still sell at a &#8216;good enough&#8217; where good enough can be astonishingly bad.  Features though, don&#8217;t seem to have that luxury.  On some level it has to offer something good enough to sell.   My son plays all kinds of online games with his friends that validates this in my mind time and time again.</p>
<p>The first guy that I had that taught me how to develop still resonates with me &#8230; &#8220;Make it work,  make it maintainable, make it reliable, make it fast.  Repeat.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

