<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <link>http://persumi.com/u/fredwu/tech/e/blog/t/inherited_resources</link>
    <generator>Persumi - Level up your writing and blogging with AI</generator>
    <category>Blog</category>
    <category>Tech</category>
    <pubDate>Sat, 16 May 2026 05:01:53 +0000</pubDate>
    <description/>
    <title>Blog (inherited_resources) - Fred Wu&apos;s Tech</title>
    <atom:link type="application/rss+xml" rel="self" href="http://persumi.com/u/fredwu/tech/e/blog/t/inherited_resources/feed/rss"></atom:link>
    <item>
      <pubDate>Thu, 05 Aug 2010 11:16:53 +0000</pubDate>
      <guid>http://persumi.com/u/fredwu/tech/e/blog/p/rails-releasing-inherited-resources-views-dry-your-view-files</guid>
      <comments>http://persumi.com/u/fredwu/tech/e/blog/p/rails-releasing-inherited-resources-views-dry-your-view-files</comments>
      <category>Blog</category>
      <category>Tech</category>
      <author>ifredwu@gmail.com (Fred Wu)</author>
      <description>&lt;![CDATA[&lt;p&gt;
Using &lt;a href=&quot;http://github.com/josevalim/inherited_resources&quot;&gt;Inherited Resources&lt;/a&gt; is an excellent way to reduce the amount of repetition in your controllers. But what about views? A lot of times resources share the same views, so why not DRY ‘em up using &lt;strong&gt;Inherited Resources Views&lt;/strong&gt;!&lt;/p&gt;
&lt;p&gt;
&lt;a href=&quot;http://github.com/fredwu/inherited_resources_views&quot;&gt;Go check out the code!&lt;/a&gt; :-)&lt;/p&gt;
]]&gt;</description>
      <link>http://persumi.com/u/fredwu/tech/e/blog/p/rails-releasing-inherited-resources-views-dry-your-view-files</link>
      <title>[Rails] Releasing Inherited Resources Views - DRY Your View Files</title>
    </item>
  </channel>
</rss>