<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>GamerDNA Blog - Latest Comments in Are you a Ninja Developer?</title><link>http://gamerdnablog.disqus.com/</link><description>None</description><atom:link href="https://gamerdnablog.disqus.com/are_you_a_ninja_developer/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 21 Jan 2009 16:14:05 -0000</lastBuildDate><item><title>Re: Are you a Ninja Developer?</title><link>http://blog.gamerdna.com/2008/01/23/are-you-a-ninja-developer/#comment-15069082</link><description>&lt;p&gt;My friend started "porting" his very popular, high-trafficked PHP-based web site to RoR a few years ago. He did it in a 100% incremental way, employing most XP practices (including TDD). It's now completely RoR and scaling quite well. It wasn't easy, and some trails were blazed in the process, but it is doable.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Hargett</dc:creator><pubDate>Wed, 21 Jan 2009 16:14:05 -0000</pubDate></item><item><title>Re: Are you a Ninja Developer?</title><link>http://blog.gamerdna.com/2008/01/23/are-you-a-ninja-developer/#comment-15069081</link><description>&lt;p&gt;We will scale by being smart. The power of RoR is for rapid development, but you still have to make a second pass as dictated by popularity, tweaking your SQL, your joins, etc. We can also convert popular areas to service architecture running on my streamlined technologies and put in XML caching layers.&lt;/p&gt;&lt;p&gt;In the end, I think anything can scale if you are smart about it... and I that is what we will TRY and be... :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Trapper</dc:creator><pubDate>Thu, 22 May 2008 16:52:14 -0000</pubDate></item><item><title>Re: Are you a Ninja Developer?</title><link>http://blog.gamerdna.com/2008/01/23/are-you-a-ninja-developer/#comment-15069080</link><description>&lt;p&gt;I am all about RoR but how will you compensate for RoR's inability to scale.  The purpose of your site is to reach out to the masses, however RoR doesn't really seem to provide you that flexibility and will cost a lot of money to support you hardware-wise.  I'm working with RoR now on a project to satisfy a requirement but its on a much smaller scale.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">praelian</dc:creator><pubDate>Tue, 20 May 2008 16:01:01 -0000</pubDate></item></channel></rss>