<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://peterbell.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Peter Bell</title>
 <link>http://peterbell.sys-con.com/</link>
 <description>Latest News from Peter Bell</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Thu, 26 Nov 2009 23:36:09 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Architecting Your ColdFusion Objects</title>
 <link>http://peterbell.sys-con.com/node/317562</link>
 <description>Once you&#039;ve learned the syntax of cfcs, one of the hardest things to do is to figure out exactly how and where to use them. The goal of this article is to run you through the most common (and useful) ways to use cfcs to make your applications easier to maintain.&lt;p&gt;&lt;a href=&quot;http://peterbell.sys-con.com/node/317562&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 24 Dec 2006 22:30:00 EST</pubDate>
 <guid isPermaLink="true">http://peterbell.sys-con.com/node/317562</guid>
 <comments>http://peterbell.sys-con.com/node/317562#feedback</comments>
</item>
<item>
 <title>CFDJ Feature — An Introduction to Intent Driven Design</title>
 <link>http://peterbell.sys-con.com/node/311316</link>
 <description>Often the hardest part of developing an application is getting agreement on what exactly it should do. Intent Driven Design (IDD) is an approach that simplifies and standardizes the process of getting detailed technical requirements from non-technical business users so you can develop more complete and consistent requirements in less time.&lt;p&gt;&lt;a href=&quot;http://peterbell.sys-con.com/node/311316&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 12 Dec 2006 12:00:00 EST</pubDate>
 <guid isPermaLink="true">http://peterbell.sys-con.com/node/311316</guid>
 <comments>http://peterbell.sys-con.com/node/311316#feedback</comments>
</item>
<item>
 <title>Encapsulating Recordsets</title>
 <link>http://peterbell.sys-con.com/node/296199</link>
 <description>One of the first things that you encounter when moving to object-oriented (OO) programming are beans. Beans are simple representations of a business object (like a user or a product) that hide all of the information stored in the bean behind methods (functions) for getting and setting the information (called, unsurprisingly, getters and setters).&lt;p&gt;&lt;a href=&quot;http://peterbell.sys-con.com/node/296199&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 09 Nov 2006 13:00:00 EST</pubDate>
 <guid isPermaLink="true">http://peterbell.sys-con.com/node/296199</guid>
 <comments>http://peterbell.sys-con.com/node/296199#feedback</comments>
</item>
</channel>
</rss>
