<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The Summer of Bloated Software</title>
	<link>http://www.rylowry.com/blog/2006/05/25/wonderful-summer-and-bloated-software/</link>
	<description>Solve two problems at once.  Feed the homeless to the hungry.</description>
	<pubDate>Sat, 05 Jul 2008 12:26:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>By: The Retrospector &#187; Blog Archive &#187; Commercial vs. Open Source: Another Point for Open Source</title>
		<link>http://www.rylowry.com/blog/2006/05/25/wonderful-summer-and-bloated-software/#comment-2</link>
		<author>The Retrospector &#187; Blog Archive &#187; Commercial vs. Open Source: Another Point for Open Source</author>
		<pubDate>Fri, 26 May 2006 13:51:33 +0000</pubDate>
		<guid>http://www.rylowry.com/blog/2006/05/25/wonderful-summer-and-bloated-software/#comment-2</guid>
					<description>[...] I stumbled onto an article in Ry Lowry&#8217;s blog that included a piece about his frustration with applying test driven development (TDD) to a commercial framework. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I stumbled onto an article in Ry Lowry&#8217;s blog that included a piece about his frustration with applying test driven development (TDD) to a commercial framework. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Jeff Wujk</title>
		<link>http://www.rylowry.com/blog/2006/05/25/wonderful-summer-and-bloated-software/#comment-3</link>
		<author>Jeff Wujk</author>
		<pubDate>Fri, 26 May 2006 18:57:56 +0000</pubDate>
		<guid>http://www.rylowry.com/blog/2006/05/25/wonderful-summer-and-bloated-software/#comment-3</guid>
					<description>Commercial framework developers aren't thinking about testability yet.  Neither are people who give them recommendations about "good practice."  

One of the worst things framework developers do is use final and sealed all over the place.  This blog talks about the problem.

http://blogs.objectmentor.com/ArticleS.MichaelFeathers.ItsTimeToDeprecateFinal</description>
		<content:encoded><![CDATA[<p>Commercial framework developers aren&#8217;t thinking about testability yet.  Neither are people who give them recommendations about &#8220;good practice.&#8221;  </p>
<p>One of the worst things framework developers do is use final and sealed all over the place.  This blog talks about the problem.</p>
<p><a href="http://blogs.objectmentor.com/ArticleS.MichaelFeathers.ItsTimeToDeprecateFinal" rel="nofollow">http://blogs.objectmentor.com/ArticleS.MichaelFeathers.ItsTimeToDeprecateFinal</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ry&#8217;s Blog &#187; Open Source: The &#8220;Just-Do-It-Yourself&#8221; Argument</title>
		<link>http://www.rylowry.com/blog/2006/05/25/wonderful-summer-and-bloated-software/#comment-7</link>
		<author>Ry&#8217;s Blog &#187; Open Source: The &#8220;Just-Do-It-Yourself&#8221; Argument</author>
		<pubDate>Wed, 31 May 2006 06:05:27 +0000</pubDate>
		<guid>http://www.rylowry.com/blog/2006/05/25/wonderful-summer-and-bloated-software/#comment-7</guid>
					<description>[...] A few of my fellow developers and I were recently tasked with bolstering the test suite which runs against our commercial framework. As I discussed in part two of The Summer of Bloated Software, HttpUnit, one of our shop&#8217;s favorite tools for testing, simply could not do the job due to the unusual way in which our commercial framework generated form fields. This meant that several important use cases could not be tested with HttpUnit, and that we were going to have to have someone manually test them. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] A few of my fellow developers and I were recently tasked with bolstering the test suite which runs against our commercial framework. As I discussed in part two of The Summer of Bloated Software, HttpUnit, one of our shop&#8217;s favorite tools for testing, simply could not do the job due to the unusual way in which our commercial framework generated form fields. This meant that several important use cases could not be tested with HttpUnit, and that we were going to have to have someone manually test them. [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
