<?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 for loop label</title>
	<atom:link href="http://blog.looplabel.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.looplabel.net</link>
	<description>programming, technology and human behavior</description>
	<lastBuildDate>Thu, 17 Nov 2011 13:56:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Best Practices for Version Control by Appropriate Checkin Comments &#171; MTR</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-24229</link>
		<dc:creator>Appropriate Checkin Comments &#171; MTR</dc:creator>
		<pubDate>Thu, 17 Nov 2011 13:56:04 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-24229</guid>
		<description>[...] One developer writes: Many developers are sloppy about commenting their changes, and some may feel that commit messages are not needed. Either they consider the changes trivial, or they argue that you can just inspect the revision history to see what was changed. However, the revision history only shows what was actually changed, not what the programmer intended to do, or why the change was made. This can be even more problematic when people don’t do fine-grained commits, but rather submit a week’s worth of changes to multiple modules in one large pile. With a fine-grained revision history, comments can be useful to distinguish trivial from non-trivial changes in the repository. In my opinion, if the changes you made are not important enough to comment on, they probably are not worth committing either. [...]</description>
		<content:encoded><![CDATA[<p>[...] One developer writes: Many developers are sloppy about commenting their changes, and some may feel that commit messages are not needed. Either they consider the changes trivial, or they argue that you can just inspect the revision history to see what was changed. However, the revision history only shows what was actually changed, not what the programmer intended to do, or why the change was made. This can be even more problematic when people don’t do fine-grained commits, but rather submit a week’s worth of changes to multiple modules in one large pile. With a fine-grained revision history, comments can be useful to distinguish trivial from non-trivial changes in the repository. In my opinion, if the changes you made are not important enough to comment on, they probably are not worth committing either. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Best Practices for Version Control by Suggestions for a good commit message: format/guideline? - Programmers Goodies</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-19798</link>
		<dc:creator>Suggestions for a good commit message: format/guideline? - Programmers Goodies</dc:creator>
		<pubDate>Mon, 04 Jul 2011 16:57:17 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-19798</guid>
		<description>[...] Here&#8217;s an extract from my recommended best practices for version control: [...]</description>
		<content:encoded><![CDATA[<p>[...] Here&#8217;s an extract from my recommended best practices for version control: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Writing a Good Technical Résumé/CV by Michelle</title>
		<link>http://blog.looplabel.net/2009/02/12/writing-a-good-technical-resume-cv/comment-page-1/#comment-16424</link>
		<dc:creator>Michelle</dc:creator>
		<pubDate>Sat, 09 Apr 2011 07:23:25 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=604#comment-16424</guid>
		<description>Its very informative blog. Thanks for posting. Additionally I would suggest to learn the employer company, learn the requirements and then create the CV in such a manner that candidate makes the employer realize that he is the one they were searching for!  This will satisfy you as well as the employer. We being a  recruitment agency, update the candidates CV since the freshers especially really find it difficult to draft it themselves. keep posting.</description>
		<content:encoded><![CDATA[<p>Its very informative blog. Thanks for posting. Additionally I would suggest to learn the employer company, learn the requirements and then create the CV in such a manner that candidate makes the employer realize that he is the one they were searching for!  This will satisfy you as well as the employer. We being a  recruitment agency, update the candidates CV since the freshers especially really find it difficult to draft it themselves. keep posting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JavaZone 2009: Utilizing Scripting in Real-World Applications by JavaZone 2010: What Clouds Are Out There and Which Do You Need? &#8211; loop label</title>
		<link>http://blog.looplabel.net/2009/09/18/javazone-2009-utilizing-scripting-in-real-world-applications/comment-page-1/#comment-7578</link>
		<dc:creator>JavaZone 2010: What Clouds Are Out There and Which Do You Need? &#8211; loop label</dc:creator>
		<pubDate>Sun, 03 Oct 2010 09:19:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.looplabel.net/?p=1212#comment-7578</guid>
		<description>[...] loop label programming, technology and human behavior   Skip to content     &#171; JavaZone 2009: Utilizing Scripting in Real-World Applications [...]</description>
		<content:encoded><![CDATA[<p>[...] loop label programming, technology and human behavior   Skip to content     &laquo; JavaZone 2009: Utilizing Scripting in Real-World Applications [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Best Practices for Version Control by Best Practices to Consider When Using a Version Control Tool &#124; Version Control Notes</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-6235</link>
		<dc:creator>Best Practices to Consider When Using a Version Control Tool &#124; Version Control Notes</dc:creator>
		<pubDate>Wed, 23 Jun 2010 00:33:30 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-6235</guid>
		<description>[...] within a version control system.  If you would like to read the full article, you can find it at: http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/.          This entry was posted in Uncategorized. Bookmark the permalink.    &#8592; Seven Basics [...]</description>
		<content:encoded><![CDATA[<p>[...] within a version control system.  If you would like to read the full article, you can find it at: <a href="http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/" rel="nofollow">http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/</a>.          This entry was posted in Uncategorized. Bookmark the permalink.    &larr; Seven Basics [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Best Practices for Version Control by naplan</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-5836</link>
		<dc:creator>naplan</dc:creator>
		<pubDate>Tue, 18 May 2010 01:49:36 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-5836</guid>
		<description>What do you think about Visual Source Safe in comparison to CVS. Thanks for the post.</description>
		<content:encoded><![CDATA[<p>What do you think about Visual Source Safe in comparison to CVS. Thanks for the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Writing a Good Technical Résumé/CV by Looking for an IT job? What your resume should have? &#124; Atlassoft Blog</title>
		<link>http://blog.looplabel.net/2009/02/12/writing-a-good-technical-resume-cv/comment-page-1/#comment-5231</link>
		<dc:creator>Looking for an IT job? What your resume should have? &#124; Atlassoft Blog</dc:creator>
		<pubDate>Tue, 06 Apr 2010 04:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=604#comment-5231</guid>
		<description>[...] are some important suggestions. But apart from this you can also read up Niniane Wang’s tips on resume [...]</description>
		<content:encoded><![CDATA[<p>[...] are some important suggestions. But apart from this you can also read up Niniane Wang’s tips on resume [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Writing a Good Technical Résumé/CV by Andreas Grech</title>
		<link>http://blog.looplabel.net/2009/02/12/writing-a-good-technical-resume-cv/comment-page-1/#comment-4303</link>
		<dc:creator>Andreas Grech</dc:creator>
		<pubDate>Mon, 01 Feb 2010 18:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=604#comment-4303</guid>
		<description>This is the post I check most when updating my CV. 

Thanks a lot for this.</description>
		<content:encoded><![CDATA[<p>This is the post I check most when updating my CV. </p>
<p>Thanks a lot for this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Best Practices for Version Control by Diego Vieira</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-4201</link>
		<dc:creator>Diego Vieira</dc:creator>
		<pubDate>Mon, 25 Jan 2010 11:32:34 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-4201</guid>
		<description>Very usefull tips!
Thanks Anders</description>
		<content:encoded><![CDATA[<p>Very usefull tips!<br />
Thanks Anders</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Best Practices for Version Control by Dave Cantrell</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-2815</link>
		<dc:creator>Dave Cantrell</dc:creator>
		<pubDate>Sat, 12 Dec 2009 00:58:01 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-2815</guid>
		<description>Anders,

Just wanted to say this is a great post. I was looking for exactly this kind of information and you summed everything up very nicely. Thanks for the info!</description>
		<content:encoded><![CDATA[<p>Anders,</p>
<p>Just wanted to say this is a great post. I was looking for exactly this kind of information and you summed everything up very nicely. Thanks for the info!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

