<?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: Elements Of Simplicity: Working Around Workarounds</title>
	<link>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/</link>
	<description>Lidor Wyssocky's Blog on Optimizing Software Development</description>
	<pubDate>Sat, 17 May 2008 04:14:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Elements Of Simplicity: Working Around Workarounds by: güzel sözler</title>
		<link>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-43552</link>
		<pubDate>Mon, 14 Apr 2008 23:11:00 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-43552</guid>
					<description>thanks for the good post..</description>
		<content:encoded><![CDATA[	<p>thanks for the good post..
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Elements Of Simplicity: Working Around Workarounds by: Travis Truman</title>
		<link>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-2322</link>
		<pubDate>Fri, 13 Oct 2006 05:25:14 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-2322</guid>
					<description>I've always been a fan of @hack when doing so in Java or JSP code. One of the nice things about this is, is if you embed it in your JavaDoc, you can always extend the Doclet parser to format it specially or somesuch so it pops out to folks not only reading the code, but reading the documentation.</description>
		<content:encoded><![CDATA[	<p>I&#8217;ve always been a fan of @hack when doing so in Java or JSP code. One of the nice things about this is, is if you embed it in your JavaDoc, you can always extend the Doclet parser to format it specially or somesuch so it pops out to folks not only reading the code, but reading the documentation.
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Elements Of Simplicity: Working Around Workarounds by: Ali Khan</title>
		<link>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-836</link>
		<pubDate>Tue, 04 Jul 2006 05:00:28 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-836</guid>
					<description>But what if you are working on code that was written by people who are no more in company and code has lot of quick-fixes, workarounds etc. and to answer support calls/fixing issues you have no other way but to play with those fixes/workarounds again and again... knowing this is making situation from bad to worse.... but timing constraints, client crying... phew!</description>
		<content:encoded><![CDATA[	<p>But what if you are working on code that was written by people who are no more in company and code has lot of quick-fixes, workarounds etc. and to answer support calls/fixing issues you have no other way but to play with those fixes/workarounds again and again&#8230; knowing this is making situation from bad to worse&#8230;. but timing constraints, client crying&#8230; phew!
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Elements Of Simplicity: Working Around Workarounds by: Lidor Wyssocky</title>
		<link>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-787</link>
		<pubDate>Wed, 28 Jun 2006 20:35:02 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-787</guid>
					<description>Just a simple pre-defined format. Something like that: 

// WORKAROUND
// Problem: 
// Solution: 

The point is that a developer working with the code will not mistake it for a permanent and well-thought of code. 

Lidor</description>
		<content:encoded><![CDATA[	<p>Just a simple pre-defined format. Something like that: </p>
	<p>// WORKAROUND<br />
// Problem:<br />
// Solution: </p>
	<p>The point is that a developer working with the code will not mistake it for a permanent and well-thought of code. </p>
	<p>Lidor
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Elements Of Simplicity: Working Around Workarounds by: y0mbo</title>
		<link>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-786</link>
		<pubDate>Wed, 28 Jun 2006 18:49:00 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-786</guid>
					<description>You suggest a method for commenting &quot;hacked&quot; code, and that it should have a specific format, but didn't provide a sample.  

What sort of formatting do you suggest?</description>
		<content:encoded><![CDATA[	<p>You suggest a method for commenting &#8220;hacked&#8221; code, and that it should have a specific format, but didn&#8217;t provide a sample.  </p>
	<p>What sort of formatting do you suggest?
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Elements Of Simplicity: Working Around Workarounds by: I can do better&#8230; a software development blog by Marcin Brzezinski &#187; I think I really am a geek!</title>
		<link>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-780</link>
		<pubDate>Wed, 28 Jun 2006 06:32:57 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/06/27/elements-of-simplicity-working-around-workarounds/#comment-780</guid>
					<description>[...] How else can you describe the constant nodding while reading an article like this? [...]</description>
		<content:encoded><![CDATA[	<p>[&#8230;] How else can you describe the constant nodding while reading an article like this? [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
