<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Clean Code on Kaan's Blog</title><link>https://kaanbardak.com/tags/clean-code/</link><description>Recent content in Clean Code on Kaan's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 17 Feb 2016 03:31:06 +0000</lastBuildDate><atom:link href="https://kaanbardak.com/tags/clean-code/rss.xml" rel="self" type="application/rss+xml"/><item><title>Effective Code Review</title><link>https://kaanbardak.com/posts/effective-code-review/</link><pubDate>Wed, 17 Feb 2016 03:31:06 +0000</pubDate><guid>https://kaanbardak.com/posts/effective-code-review/</guid><description>&lt;p&gt;&lt;img src="https://kaanbardak.com/posts/effective-code-review/wtf-per-second.jpg" alt="wtf/sec"&gt;&lt;/p&gt;
&lt;p&gt;As we all know, code review is maybe the oldest technique to stepping into the software quality assurance realm. Because of the variety of the technologies, project and team sizes, there is no code-review standard. Nevertheless, I would like to share my version I did practice.&lt;/p&gt;
&lt;p&gt;Disclaimer: This practices make more sense for the projects which use same code-bases over years (product lines) with high maintainability targeted.&lt;/p&gt;
&lt;h1 id="peer-review"&gt;Peer Review&lt;/h1&gt;
&lt;p&gt;Everybody is familiar with the peer review. Once a developer feels that his/her job is done and ready for check-in; he/she&lt;/p&gt;</description></item><item><title>Clean Coder needs more mastery</title><link>https://kaanbardak.com/posts/clean-coder-needs-more-autonomy/</link><pubDate>Sun, 30 Dec 2012 13:26:29 +0000</pubDate><guid>https://kaanbardak.com/posts/clean-coder-needs-more-autonomy/</guid><description>&lt;p&gt;&lt;img src="https://kaanbardak.com/posts/clean-coder-needs-more-autonomy/The-Clean-Coder.jpg" alt="The-Clean-Coder"&gt;&lt;/p&gt;
&lt;p&gt;I would like to share my thougths about this book I’ve read recently. The book is titled &lt;a href="https://www.amazon.co.uk/dp/0137081073/ref=as_li_ss_til?tag=publicfunctio-21&amp;amp;camp=2902&amp;amp;creative=19466&amp;amp;linkCode=as4&amp;amp;creativeASIN=0137081073&amp;amp;adid=0GABQQFTGF8K17C9PQW2&amp;amp;" target="_blank" rel="noopener"&gt;The Clean Coder&lt;/a&gt;, and its written by Robert C. Martin.&lt;/p&gt;
&lt;p&gt;Robert C. Martin (aka Uncle Bob) is known to host seminars and articles he posts on his site. And of course the books he published. I presume, the &lt;a href="https://www.amazon.co.uk/dp/0132350882/ref=as_li_ss_til?tag=publicfunctio-21&amp;amp;camp=2902&amp;amp;creative=19466&amp;amp;linkCode=as4&amp;amp;creativeASIN=0132350882&amp;amp;adid=14X5844K5VST9JFVYGFP&amp;amp;" target="_blank" rel="noopener"&gt;Clean Code&lt;/a&gt; and the &lt;a href="https://www.amazon.co.uk/dp/0131857258/ref=as_li_ss_til?tag=publicfunctio-21&amp;amp;camp=2902&amp;amp;creative=19466&amp;amp;linkCode=as4&amp;amp;creativeASIN=0131857258&amp;amp;adid=1ZE5E8ZZ8NW60EPZXVEX&amp;amp;" target="_blank" rel="noopener"&gt;Agile Patterns, Principles and Practices&lt;/a&gt; are well known.&lt;/p&gt;
&lt;p&gt;I’ve encountered many discussion forums and blogs with the subject of having the Clean Code, based on rules and principles in the book. I also participate in one of these groups that focuses on  Clean Coding in our company.  I’ve seen groups which categorize his rules and assign ranks similar to the belt system in martial arts for target achievements. I find that going a bit too far as in only following the rules blindly and completely disregarding other elements of software design. I suggest them to read another book of Uncle Bob named “The Pattern, Principles and Practices”&lt;/p&gt;</description></item></channel></rss>