<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Design Principles in Ruby on Rails - Slepi.NET</title>
    <link>http://www.slepi.net/entry/design_principles_in_ruby_on_rails</link>
    <pubDate>Wed, 19 Nov 2008 06:35:38 -0600</pubDate>
    <description>Within the last few years Ruby on Rails (RoR or just simply Rails) has gained great popularity in the way people develop web applications. It offers web developers to make an architecturally clean web application at a relatively faster time, compared to many existing technologies known. By clean architecture, I mean an application that you could painlessly maintain, change, and extend to meet the objectives of why it's built, even perhaps by someone who initially didn't develop it. For many developers such requirements are really not an easy task to accomplish, nor something that could be done quick enough to save them a moment to enjoy life. Yes, we're hopping from one project to another, time is precious.</description>
    <copyright>Copyrights 2008 Wiras Adi</copyright>
    <image>
      <url>http://www.slepi.net/images/slepinet-rss.png</url>
      <title>Design Principles in Ruby on Rails - Slepi.NET</title>
      <link>http://www.slepi.net</link>
    </image>
  </channel>
</rss>
