<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Why You Need A Case Statement</title>
	<atom:link href="http://www.jasonmcneal.com/2010/03/why-you-need-a-case-statement/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jasonmcneal.com/2010/03/why-you-need-a-case-statement/</link>
	<description>Know Donors. Know Success.</description>
	<lastBuildDate>Mon, 26 Dec 2011 17:59:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jack Ewing</title>
		<link>http://www.jasonmcneal.com/2010/03/why-you-need-a-case-statement/comment-page-1/#comment-141</link>
		<dc:creator>Jack Ewing</dc:creator>
		<pubDate>Thu, 01 Apr 2010 13:30:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasonmcneal.com/?p=1217#comment-141</guid>
		<description>Once again, Jason, is clear and concise in his blog, this time on the value of case statements.  Jason and Doug Mason helped us develop our case statement but, by far, the greatest value came from the process of thinking through what we needed to be able to say and how to communicate that.  We have not used the case statement as much as we anticipated but we have used the case with its clarity of focus over and over again.</description>
		<content:encoded><![CDATA[<p>Once again, Jason, is clear and concise in his blog, this time on the value of case statements.  Jason and Doug Mason helped us develop our case statement but, by far, the greatest value came from the process of thinking through what we needed to be able to say and how to communicate that.  We have not used the case statement as much as we anticipated but we have used the case with its clarity of focus over and over again.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

