<?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: Changes Are Expensive</title>
	<atom:link href="http://littlesquare.com/2007/12/changes-are-expensive/feed/" rel="self" type="application/rss+xml" />
	<link>http://littlesquare.com/2007/12/changes-are-expensive/</link>
	<description>Just a little square in a sea of blogs</description>
	<lastBuildDate>Wed, 08 Feb 2012 14:58:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Abhijit Nadgouda</title>
		<link>http://littlesquare.com/2007/12/changes-are-expensive/#comment-110</link>
		<dc:creator>Abhijit Nadgouda</dc:creator>
		<pubDate>Sun, 30 Dec 2007 06:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.jordens.org/2007/12/10/changes-are-expensive/#comment-110</guid>
		<description>Thanks for extending the discussion. As you guessed right, I am in India, but I have not been doing a lot of outsourced work. I have been involved in writing some APIs which end up in other developers&#039; hands, and that is when the test suites are useful. As you hinted, they might not be suitable for the end users.

I wholeheartedly agree with you about being a proactive individual, and that I think can ease a lot about making changes.

When I wrote this, I came across more than a couple of instances where the change was measured in the lines of code. I think that is a poor measurement. The impact can exceed much farther, and I believe can be much fatal.

Changes are of course inevitable, but it equally important to be prepared for changes and realize that every change will have a cost, however small it is. This realization can help managing the work much better.</description>
		<content:encoded><![CDATA[<p>Thanks for extending the discussion. As you guessed right, I am in India, but I have not been doing a lot of outsourced work. I have been involved in writing some APIs which end up in other developers&#8217; hands, and that is when the test suites are useful. As you hinted, they might not be suitable for the end users.</p>
<p>I wholeheartedly agree with you about being a proactive individual, and that I think can ease a lot about making changes.</p>
<p>When I wrote this, I came across more than a couple of instances where the change was measured in the lines of code. I think that is a poor measurement. The impact can exceed much farther, and I believe can be much fatal.</p>
<p>Changes are of course inevitable, but it equally important to be prepared for changes and realize that every change will have a cost, however small it is. This realization can help managing the work much better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

