<?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: Act Like a Senior Developer &#8211; About Clean Code</title>
	<atom:link href="http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/</link>
	<description>Nobody can be perfect, but you can think better, design better, and always use baby steps!</description>
	<lastBuildDate>Tue, 22 Nov 2011 10:53:40 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Me</title>
		<link>http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/comment-page-1/#comment-5358</link>
		<dc:creator>Me</dc:creator>
		<pubDate>Wed, 06 Jan 2010 16:11:15 +0000</pubDate>
		<guid isPermaLink="false">http://isagoksu.com/?p=603#comment-5358</guid>
		<description>&lt;p&gt;I have only one rot. Do not have any rots!
All rots are just someone&#039;s problem.
This article is problem of guy who has problems with code understanding. He needs more practice and this problem will be solved.
One man&#039;s best practice is another worst nightmare.
Brake the rules.
Do whatever you want.
Do wherever you want.
Do everything your way.
Never follow any loosers rules.
No more &quot;this sould be done this way&quot;.
Have your own opinion.
Be free.
;)
I did not tell you to do wrong!
Just do it your way.
Your way is the best way.
Let loosers to make rots of doing your way.
Loosers create rots and design patterns because they have no brains to think and understand. They have no fantazy to create. Only thing they can is to copy.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I have only one rot. Do not have any rots!
All rots are just someone&#8217;s problem.
This article is problem of guy who has problems with code understanding. He needs more practice and this problem will be solved.
One man&#8217;s best practice is another worst nightmare.
Brake the rules.
Do whatever you want.
Do wherever you want.
Do everything your way.
Never follow any loosers rules.
No more &#8220;this sould be done this way&#8221;.
Have your own opinion.
Be free.
;)
I did not tell you to do wrong!
Just do it your way.
Your way is the best way.
Let loosers to make rots of doing your way.
Loosers create rots and design patterns because they have no brains to think and understand. They have no fantazy to create. Only thing they can is to copy.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Giorgio Sironi</title>
		<link>http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/comment-page-1/#comment-4814</link>
		<dc:creator>Giorgio Sironi</dc:creator>
		<pubDate>Sun, 06 Dec 2009 16:03:15 +0000</pubDate>
		<guid isPermaLink="false">http://isagoksu.com/?p=603#comment-4814</guid>
		<description>&lt;p&gt;Good low-level advice (low in the sense that it is closer to the code than to the design :).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Good low-level advice (low in the sense that it is closer to the code than to the design :).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Acheson</title>
		<link>http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/comment-page-1/#comment-4741</link>
		<dc:creator>Tim Acheson</dc:creator>
		<pubDate>Thu, 03 Dec 2009 14:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://isagoksu.com/?p=603#comment-4741</guid>
		<description>&lt;p&gt;This is a nice refresher on some best practices in coding standards, thanks!&lt;/p&gt;

&lt;p&gt;We use the ReSharper plug-in in Visual Studio 2008 which is very good at highlighting the worst bad practices, and it can often do any necessary recactoring for you with one click.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This is a nice refresher on some best practices in coding standards, thanks!</p>

<p>We use the ReSharper plug-in in Visual Studio 2008 which is very good at highlighting the worst bad practices, and it can often do any necessary recactoring for you with one click.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: cortex</title>
		<link>http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/comment-page-1/#comment-4711</link>
		<dc:creator>cortex</dc:creator>
		<pubDate>Tue, 01 Dec 2009 16:15:58 +0000</pubDate>
		<guid isPermaLink="false">http://isagoksu.com/?p=603#comment-4711</guid>
		<description>&lt;p&gt;quite likely this was your intention:&lt;/p&gt;

&lt;p&gt;// SOLUTION: how about this? I stil don&#039;t know why you need continue there?
for (int i=0; i &lt; items.size(); i++) {
    if (isVisible(items.get(i))) {
        doThis(); 
    }
}&lt;/p&gt;

&lt;p&gt;cx&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>quite likely this was your intention:</p>

<p>// SOLUTION: how about this? I stil don&#8217;t know why you need continue there?
for (int i=0; i &lt; items.size(); i++) {
    if (isVisible(items.get(i))) {
        doThis(); 
    }
}</p>

<p>cx</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Pavel</title>
		<link>http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/comment-page-1/#comment-4682</link>
		<dc:creator>Pavel</dc:creator>
		<pubDate>Mon, 30 Nov 2009 08:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://isagoksu.com/?p=603#comment-4682</guid>
		<description>&lt;p&gt;Thank you Isa. We have to refresh our mind from time to time with such nice topics. The problem is that 99% of developers (including myself) swear at bad code but don&#039;t improve it after review :)
Appreciate your great work. Keep writing!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thank you Isa. We have to refresh our mind from time to time with such nice topics. The problem is that 99% of developers (including myself) swear at bad code but don&#8217;t improve it after review :)
Appreciate your great work. Keep writing!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Java bookmark links, Nov 2009 – Week4 &#124; bookmark-link</title>
		<link>http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/comment-page-1/#comment-4662</link>
		<dc:creator>Java bookmark links, Nov 2009 – Week4 &#124; bookmark-link</dc:creator>
		<pubDate>Sun, 29 Nov 2009 08:53:10 +0000</pubDate>
		<guid isPermaLink="false">http://isagoksu.com/?p=603#comment-4662</guid>
		<description>&lt;p&gt;[...] about how to act like a senior developer coding , Ifs statement, loops statement and many best [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] about how to act like a senior developer coding , Ifs statement, loops statement and many best [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/comment-page-1/#comment-4642</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sat, 28 Nov 2009 23:00:31 +0000</pubDate>
		<guid isPermaLink="false">http://isagoksu.com/?p=603#comment-4642</guid>
		<description>&lt;p&gt;It is not clear what you intend to do with the last &quot;Stupid Loop&quot; still. 
In the bad example you return items(0) if isVisible is true. The looop is not needed at all. You do the same in the good example, but don&#039;t change the isVisible flag.  In the previous example, I would put the isVisible outside the loop.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It is not clear what you intend to do with the last &#8220;Stupid Loop&#8221; still. 
In the bad example you return items(0) if isVisible is true. The looop is not needed at all. You do the same in the good example, but don&#8217;t change the isVisible flag.  In the previous example, I would put the isVisible outside the loop.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Max&#8217; Lesestoff zum Wochenende &#124; PHP hates me - Der PHP Blog</title>
		<link>http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/comment-page-1/#comment-4628</link>
		<dc:creator>Max&#8217; Lesestoff zum Wochenende &#124; PHP hates me - Der PHP Blog</dc:creator>
		<pubDate>Sat, 28 Nov 2009 05:59:54 +0000</pubDate>
		<guid isPermaLink="false">http://isagoksu.com/?p=603#comment-4628</guid>
		<description>&lt;p&gt;[...] von Continous Integration in Arbit   I can haz lolSQL? – Aaron Bassett SQL endlich in sexy!     Act Like a Senior Developer – About Clean Code hmmm   Share this on del.icio.usShare this on TechnoratiAdd this to Mister WongStumble upon [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] von Continous Integration in Arbit   I can haz lolSQL? – Aaron Bassett SQL endlich in sexy!     Act Like a Senior Developer – About Clean Code hmmm   Share this on del.icio.usShare this on TechnoratiAdd this to Mister WongStumble upon [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Yusuf Arslan</title>
		<link>http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/comment-page-1/#comment-4621</link>
		<dc:creator>Yusuf Arslan</dc:creator>
		<pubDate>Fri, 27 Nov 2009 23:43:04 +0000</pubDate>
		<guid isPermaLink="false">http://isagoksu.com/?p=603#comment-4621</guid>
		<description>&lt;p&gt;Making code simpler is relocating the complexity. There is no method to eliminate it. The art is achieving the right balance. And usually art is not achievable by following some simple rules or a check list.&lt;/p&gt;

&lt;p&gt;Your general point is really valuable and well explained with real life examples.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Making code simpler is relocating the complexity. There is no method to eliminate it. The art is achieving the right balance. And usually art is not achievable by following some simple rules or a check list.</p>

<p>Your general point is really valuable and well explained with real life examples.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Isa Goksu</title>
		<link>http://isagoksu.com/2009/development/agile-development/act-like-a-senior-developer-about-clean-code/comment-page-1/#comment-4614</link>
		<dc:creator>Isa Goksu</dc:creator>
		<pubDate>Fri, 27 Nov 2009 18:20:49 +0000</pubDate>
		<guid isPermaLink="false">http://isagoksu.com/?p=603#comment-4614</guid>
		<description>&lt;p&gt;@vdaburon, I think that one is a good idea.&lt;/p&gt;

&lt;p&gt;@gervais, as I told @laurent; if you can write your code like a poem, then I wouldn&#039;t mind. But honestly, I haven&#039;t seen any guy that can write a poem-like codes in my whole career. Even you code it like that, someone after you will come and change the all the rhyme of your code, and it will be unreadable (mess) later on. Having a huge methods are big signs of incorrect responsibility assignments. I&#039;d say if you have a code like that and you have to do it that way, it&#039;s very likely to move that logic to another class which can take certain arguments while processing. Then it would be more testable, and you would satisfy SRP in your base class and new class.&lt;/p&gt;

&lt;p&gt;And one more thing to whole comments: These are not the codes that I invent to satisfy article, these are the codes that I saw written by different senior guys which pisses me off. And as I mentioned in the article, this article is written for my relaxation. Thanks for great interest, everyone is welcome to contribute more techniques or samples. And keep in mind no one has to agree with me ;)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@vdaburon, I think that one is a good idea.</p>

<p>@gervais, as I told @laurent; if you can write your code like a poem, then I wouldn&#8217;t mind. But honestly, I haven&#8217;t seen any guy that can write a poem-like codes in my whole career. Even you code it like that, someone after you will come and change the all the rhyme of your code, and it will be unreadable (mess) later on. Having a huge methods are big signs of incorrect responsibility assignments. I&#8217;d say if you have a code like that and you have to do it that way, it&#8217;s very likely to move that logic to another class which can take certain arguments while processing. Then it would be more testable, and you would satisfy SRP in your base class and new class.</p>

<p>And one more thing to whole comments: These are not the codes that I invent to satisfy article, these are the codes that I saw written by different senior guys which pisses me off. And as I mentioned in the article, this article is written for my relaxation. Thanks for great interest, everyone is welcome to contribute more techniques or samples. And keep in mind no one has to agree with me ;)</p>]]></content:encoded>
	</item>
</channel>
</rss>

