<?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: Coding for the unexpected</title>
	<atom:link href="http://www.onlineaspect.com/2009/08/31/coding-for-the-unexpected/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.onlineaspect.com/2009/08/31/coding-for-the-unexpected/</link>
	<description>a blog about building stuff on the web</description>
	<lastBuildDate>Thu, 29 Jul 2010 18:05:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: grokcore</title>
		<link>http://www.onlineaspect.com/2009/08/31/coding-for-the-unexpected/comment-page-1/#comment-708</link>
		<dc:creator>grokcore</dc:creator>
		<pubDate>Fri, 11 Sep 2009 00:02:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.onlineaspect.com/?p=518#comment-708</guid>
		<description>You are just going through a learning curve, one that lasts for years. 
 
I think those kinks are just death throws.   The old web is dying.   The lines are blurring and becoming a landscape. 
 
Webhooks.   PubSubs (e.g. pubsubhubbub).  ATOM / RSS integration (it is really amazing what you can do with an Atom). 
 
The crude, slow internet is dissolving with it&#039;s content scattered everywhere.   I see massive content pools to wade through, high speed MemCached servers dishing out indexes &amp; references for it all, all wrapped up nicely in flexible metadata.   
 
Your disenchanted view of dealing with unsanitized input, overflowing storage and hardware failures can all go in the trash if you&#039;ve got all your data on an Amazon S3 account.   Or heck, grab VMWare, install a view servers in a cluster formation and go to school (totally impractical for production, but great for learning). 
 
Crazy stuff coming down the pipes.   Cut your teeth on the edge of the net ;) </description>
		<content:encoded><![CDATA[<p>You are just going through a learning curve, one that lasts for years. </p>
<p>I think those kinks are just death throws.   The old web is dying.   The lines are blurring and becoming a landscape. </p>
<p>Webhooks.   PubSubs (e.g. pubsubhubbub).  ATOM / RSS integration (it is really amazing what you can do with an Atom). </p>
<p>The crude, slow internet is dissolving with it&#039;s content scattered everywhere.   I see massive content pools to wade through, high speed MemCached servers dishing out indexes &amp; references for it all, all wrapped up nicely in flexible metadata.   </p>
<p>Your disenchanted view of dealing with unsanitized input, overflowing storage and hardware failures can all go in the trash if you&#039;ve got all your data on an Amazon S3 account.   Or heck, grab VMWare, install a view servers in a cluster formation and go to school (totally impractical for production, but great for learning). </p>
<p>Crazy stuff coming down the pipes.   Cut your teeth on the edge of the net <img src='http://www.onlineaspect.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olafur Waage</title>
		<link>http://www.onlineaspect.com/2009/08/31/coding-for-the-unexpected/comment-page-1/#comment-668</link>
		<dc:creator>Olafur Waage</dc:creator>
		<pubDate>Tue, 01 Sep 2009 01:10:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.onlineaspect.com/?p=518#comment-668</guid>
		<description>All code is, is an algorithm to some process that works for all possible cases. And what you&#039;re seeing there (in most cases you point out) is an algorithm that didn&#039;t work for all possible cases.  
 
Which is close to impossible in a very complex program. </description>
		<content:encoded><![CDATA[<p>All code is, is an algorithm to some process that works for all possible cases. And what you&#039;re seeing there (in most cases you point out) is an algorithm that didn&#039;t work for all possible cases. </p>
<p>Which is close to impossible in a very complex program.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
