<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
     xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
     xmlns:wfw="http://wellformedweb.org/CommentAPI/"
     xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>James Crasta</title>
    <description>James's rants and revelations</description>
    <atom:link href="http://www.crasta.com/blog/feed/rss.xml" rel="self" type="application/rss+xml" />
    <link>http://www.crasta.com/</link>
    <language>en</language>
    <lastBuildDate>Thu, 03 Dec 2009 00:00:00 -0500</lastBuildDate>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>

    
    <item>
        <title>The Framework Design Balancing-act</title>
        <link>http://www.crasta.com/blog/2009-12-03/framework_design_balancing_act</link>
        <guid isPermaLink="false">tag,crasta.com,2009-12-03:framework_design_balancing_act</guid>
        <pubDate>Thu, 03 Dec 2009 00:00:00 -0500</pubDate>
        
        <author>contact@jamescrasta.com (James Crasta)</author> 
        <description>In the Python web development world, we have become very familiar with the word &#39;framework.&#39; Most of us are using at least one, and some of us are guilty of writing our own, as well. Recently I was involved in an IRC discussion on the merits of the various web frameworks, and naturally this is about as vicious a conversation as discussing text editors of choice. A topic which came up during that discussion was the ability to start writing your code with a minimum of writing configs or other ...</description>
    </item>
    
  </channel>
</rss>