<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The (Semi) Myth Of YAGNI</title>
	<link>http://blog.qualityaspect.com/2006/06/10/the-semi-myth-of-yagni/</link>
	<description>Lidor Wyssocky's Blog on Optimizing Software Development</description>
	<pubDate>Sun, 27 Jul 2008 02:34:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on The (Semi) Myth Of YAGNI by: Framework Effective Communication</title>
		<link>http://blog.qualityaspect.com/2006/06/10/the-semi-myth-of-yagni/#comment-34977</link>
		<pubDate>Tue, 05 Feb 2008 17:47:24 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/06/10/the-semi-myth-of-yagni/#comment-34977</guid>
					<description>&lt;strong&gt;Communication - Key to Effective Parenting&lt;/strong&gt;

Exasperated parents often tell child counselors that they have almost no communication with their children. Once a child feels that she is growing up, especially at the onset of adolescence, she will start to distance herself from you and begin to talk...</description>
		<content:encoded><![CDATA[	<p><strong>Communication - Key to Effective Parenting</strong></p>
	<p>Exasperated parents often tell child counselors that they have almost no communication with their children. Once a child feels that she is growing up, especially at the onset of adolescence, she will start to distance herself from you and begin to talk&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on The (Semi) Myth Of YAGNI by: Vikrama Dhiman</title>
		<link>http://blog.qualityaspect.com/2006/06/10/the-semi-myth-of-yagni/#comment-33317</link>
		<pubDate>Sat, 12 Jan 2008 12:32:47 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/06/10/the-semi-myth-of-yagni/#comment-33317</guid>
					<description>Nice post. However, it might be useful to take YAGNI as the question and not the answer. The best architectures evolve but if your project adds value by deciding on an architecture upfront - its always useful to go for it. Thats not &quot;always&quot; the case but not to say that can't be the case. Any which way, if you are making a decision right now, you would always have a solid case for why you are doing it right now. The solid case generally comes from cost-opportunity argument. If something has a solid argument backing it, it would always be a top priority and you would need it. As you would need it, it would be YAGNI :)</description>
		<content:encoded><![CDATA[	<p>Nice post. However, it might be useful to take YAGNI as the question and not the answer. The best architectures evolve but if your project adds value by deciding on an architecture upfront - its always useful to go for it. Thats not &#8220;always&#8221; the case but not to say that can&#8217;t be the case. Any which way, if you are making a decision right now, you would always have a solid case for why you are doing it right now. The solid case generally comes from cost-opportunity argument. If something has a solid argument backing it, it would always be a top priority and you would need it. As you would need it, it would be YAGNI :)
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on The (Semi) Myth Of YAGNI by: Brooks Moses</title>
		<link>http://blog.qualityaspect.com/2006/06/10/the-semi-myth-of-yagni/#comment-1667</link>
		<pubDate>Tue, 05 Sep 2006 01:47:23 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/06/10/the-semi-myth-of-yagni/#comment-1667</guid>
					<description>It occurs to me (coming back to this a while later) that, if YAGNI is a good argument for code, it is an equally good argument for the comments in the code.  Most comments are written for the hypothetical person who's reading the code some months from now, not the person who's writing it today or tomorrow.

I think this constitutes a reductio ad absurdum proof that YAGNI is not always justified.</description>
		<content:encoded><![CDATA[	<p>It occurs to me (coming back to this a while later) that, if YAGNI is a good argument for code, it is an equally good argument for the comments in the code.  Most comments are written for the hypothetical person who&#8217;s reading the code some months from now, not the person who&#8217;s writing it today or tomorrow.</p>
	<p>I think this constitutes a reductio ad absurdum proof that YAGNI is not always justified.
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on The (Semi) Myth Of YAGNI by: KB</title>
		<link>http://blog.qualityaspect.com/2006/06/10/the-semi-myth-of-yagni/#comment-566</link>
		<pubDate>Tue, 13 Jun 2006 15:40:32 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/06/10/the-semi-myth-of-yagni/#comment-566</guid>
					<description>This is so obvious that there wouldn't even be the need of mentioning it, had not the Agile warmongers brainwashed the rest of the community.  Any thinking person should realize that following any single methodology to the extreme will not pay off in the end.  It's the law of moderation!</description>
		<content:encoded><![CDATA[	<p>This is so obvious that there wouldn&#8217;t even be the need of mentioning it, had not the Agile warmongers brainwashed the rest of the community.  Any thinking person should realize that following any single methodology to the extreme will not pay off in the end.  It&#8217;s the law of moderation!
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on The (Semi) Myth Of YAGNI by: pliantalliance.org &#187; YAGNI or will you?</title>
		<link>http://blog.qualityaspect.com/2006/06/10/the-semi-myth-of-yagni/#comment-556</link>
		<pubDate>Mon, 12 Jun 2006 14:20:00 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/06/10/the-semi-myth-of-yagni/#comment-556</guid>
					<description>[...] An excellent post questioning whether the oft heard Agile zealot cry of YAGNI is always justified. Lidor doesn&amp;#8217;t say YAGNI should be abandoned or that BDUF is the way to go. He says quite pliantly that although YAGNI makes sense on the surface, &amp;#8220;reality is somewhat more complex&amp;#8221; and sometimes making the bet to invest in the future based on experience and the context you are in is a good bet and is the right thing to do. [...]</description>
		<content:encoded><![CDATA[	<p>[&#8230;] An excellent post questioning whether the oft heard Agile zealot cry of YAGNI is always justified. Lidor doesn&#8217;t say YAGNI should be abandoned or that BDUF is the way to go. He says quite pliantly that although YAGNI makes sense on the surface, &#8220;reality is somewhat more complex&#8221; and sometimes making the bet to invest in the future based on experience and the context you are in is a good bet and is the right thing to do. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
