<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
	<channel>
		<title>gdp's Comments</title>
		<language>en-us</language>
		<link>https://www.intensedebate.com/users/503744</link>
		<description>Comments by engineyard</description>
<item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment43653854</link>
<description>Feedback seems to be the contest was too complex for people to grok easily. We&amp;#039;re not extending the current contest - but plan to make the next one a bit easier to approach </description>
<pubDate>Tue, 17 Nov 2009 22:53:51 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment43653854</guid>
</item><item>
<title>Union Station : Programming Contest! And the Challenge is...Measure Rails Momentum</title>
<link>http://www.engineyard.com/blog/2009/programming-contest-and-the-challenge-is-measure-rails-momentum/#IDComment43025783</link>
<description>Jeremy, Twitter info caching is simply an exception and a practical concession to Twitter rate limiting. There are 15k twitter ID&amp;#039;s to lookup and there&amp;#039;s no way that there are enough white-listed developers to provide a stateless lookup service. </description>
<pubDate>Fri, 13 Nov 2009 04:13:50 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/programming-contest-and-the-challenge-is-measure-rails-momentum/#IDComment43025783</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment42172740</link>
<description>Well I would guess this is a neat way of implementing a subroutine that assembles a chain of other wasepoints, but I guess you&amp;#039;re going to try to hack the program counter so that you get a hint that an incoming message is actually a return from a sub-routine?  This would not be kosher. I will add restrictions on PC modification that makes this more explicit. </description>
<pubDate>Fri, 6 Nov 2009 00:33:21 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment42172740</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment42171590</link>
<description>Hi anonymous, we have to be able to verify the winning computation with our own kickoff message, so the first part won&amp;#039;t be an issue. The second part yes might be an issue, but the computation will be difficult enough that people will need to use multiple points for the solution. We will also more definition on the scope of a WASE point. </description>
<pubDate>Fri, 6 Nov 2009 00:27:31 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment42171590</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment42127575</link>
<description>Well after you parse the message: If there are three bitly&amp;#039;s, then they are output, input1, and input 2 If there are two bitly&amp;#039;s, then they are output, input If there is one bitly, then that bitly is both input and output  Each WASEpoint is free to decide whether it will accept multiple inputs, or emit a message with multiple inputs. You have to read the doc or code for a WASEpoint to decide whether you can use it or not. </description>
<pubDate>Thu, 5 Nov 2009 17:50:00 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment42127575</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment42127080</link>
<description>sorry, looks like no PHP </description>
<pubDate>Thu, 5 Nov 2009 17:46:25 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment42127080</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment42121294</link>
<description>ok Jon Crosby has volunteered to review any Scala winner! Scala is in! </description>
<pubDate>Thu, 5 Nov 2009 16:53:05 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment42121294</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41978404</link>
<description>Incrementing &amp;amp; forward jumps is ok. </description>
<pubDate>Wed, 4 Nov 2009 19:48:26 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41978404</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41978358</link>
<description>If we can get an engineyard developer willing to review scala entries we&amp;#039;ll add it. Stay tuned. </description>
<pubDate>Wed, 4 Nov 2009 19:47:50 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41978358</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41722262</link>
<description>Well, we wanted to give you the basics first so you can get started on the parsing/http/twitter foundations without giving people who happened to read the post early, first dibs on interesting WASEpoints. But without getting into too specifics, one of the challenge computations will be math based, and one will be text based. </description>
<pubDate>Tue, 3 Nov 2009 21:09:24 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41722262</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41720843</link>
<description>Urg. Reviewing oversight -- the POSTs, should, of course, be PUTs -- since the WASEpoint is asking to replace the existing resource at that location. </description>
<pubDate>Tue, 3 Nov 2009 21:05:58 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41720843</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41719830</link>
<description>You are correct -- this is now corrected </description>
<pubDate>Tue, 3 Nov 2009 21:03:39 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41719830</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41719717</link>
<description>Hi CBE -- latest update should have cleaned up the last inconsistencies. </description>
<pubDate>Tue, 3 Nov 2009 21:03:29 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41719717</guid>
</item><item>
<title>Union Station : Win a Motorola DROID Programming Contest: &quot;Worst App Server Technology Ever&quot;</title>
<link>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41701124</link>
<description>Hi Lee. It seems as if the link you point to was about someone posting an unauthorized copy of WASTE as free software. WASTE seems to be in continuing development: &lt;a href=&quot;http://bit.ly/2dcsAC.&quot; target=&quot;_blank&quot;&gt;http://bit.ly/2dcsAC.&lt;/a&gt; But since WASTE is in the same general area as the contest, we&amp;#039;ll make things simpler and change the terminology to WASE &amp;quot;Worst App Server Ever&amp;quot; </description>
<pubDate>Tue, 3 Nov 2009 20:23:01 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/win-a-motorola-droid-programming-contest-worst-app-server-technology-ever/#IDComment41701124</guid>
</item><item>
<title>Union Station : Programming Contest! Win iPhone 3GS &amp; $2,000 Cloud Credit</title>
<link>http://www.engineyard.com/blog/2009/programming-contest-win-iphone-3gs-2k-cloud-credit/#IDComment27776786</link>
<description>We&amp;#039;re posting the challenge at noon pacific time-- as we mentioned in the blog post, you will have 30 hours to search before the 6pm cutoff tomorrow.  </description>
<pubDate>Mon, 20 Jul 2009 16:52:17 +0000</pubDate>
<guid>http://www.engineyard.com/blog/2009/programming-contest-win-iphone-3gs-2k-cloud-credit/#IDComment27776786</guid>
</item><item>
<title>Engine Yard Blog (STAGING) : Hello world, this is Engine Yard Staging</title>
<link>http://staging.engineyard.com/blog/index.php/2009/05/hello-world/#IDComment27375926</link>
<description>Hello world </description>
<pubDate>Wed, 15 Jul 2009 21:38:56 +0000</pubDate>
<guid>http://staging.engineyard.com/blog/index.php/2009/05/hello-world/#IDComment27375926</guid>
</item>	</channel>
</rss>