<?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: Back to basics: good source control check-in habits</title>
	<atom:link href="http://richarddingwall.name/2008/11/23/back-to-basics-good-source-control-check-in-habits/feed/" rel="self" type="application/rss+xml" />
	<link>http://richarddingwall.name/2008/11/23/back-to-basics-good-source-control-check-in-habits/</link>
	<description>The adventures of a young kiwi software developer in London</description>
	<lastBuildDate>Tue, 31 Jan 2012 19:56:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tim Reynolds</title>
		<link>http://richarddingwall.name/2008/11/23/back-to-basics-good-source-control-check-in-habits/comment-page-1/#comment-1496</link>
		<dc:creator>Tim Reynolds</dc:creator>
		<pubDate>Mon, 08 Dec 2008 00:47:12 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=632#comment-1496</guid>
		<description>Nice post. Thank you for the info. Keep it up.</description>
		<content:encoded><![CDATA[<p>Nice post. Thank you for the info. Keep it up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tech Per</title>
		<link>http://richarddingwall.name/2008/11/23/back-to-basics-good-source-control-check-in-habits/comment-page-1/#comment-1404</link>
		<dc:creator>Tech Per</dc:creator>
		<pubDate>Thu, 27 Nov 2008 19:47:15 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=632#comment-1404</guid>
		<description>Hi, good post. I agree with a lot of it, though not all of it.

About using coarse grained checkins. Yes, in the (simple) example you give, it makes sense. But I do think one should take extreme care with such an advice, to not end up in the opposite situation, where everything is held back, until everything is done.

It can be equally as bad, when someone only checks in with 4-5 days, maybe even a full week, interval, with a huge bunch of changes.

In addition to this, early and often integration also makes it more evident what people are doing. This can help keep people from doing pointless work, that isn&#039;t in the value stream map.

One last thing: You forgot the advice to always update locally, before committing :-)</description>
		<content:encoded><![CDATA[<p>Hi, good post. I agree with a lot of it, though not all of it.</p>
<p>About using coarse grained checkins. Yes, in the (simple) example you give, it makes sense. But I do think one should take extreme care with such an advice, to not end up in the opposite situation, where everything is held back, until everything is done.</p>
<p>It can be equally as bad, when someone only checks in with 4-5 days, maybe even a full week, interval, with a huge bunch of changes.</p>
<p>In addition to this, early and often integration also makes it more evident what people are doing. This can help keep people from doing pointless work, that isn&#8217;t in the value stream map.</p>
<p>One last thing: You forgot the advice to always update locally, before committing :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Holy</title>
		<link>http://richarddingwall.name/2008/11/23/back-to-basics-good-source-control-check-in-habits/comment-page-1/#comment-1379</link>
		<dc:creator>Jakub Holy</dc:creator>
		<pubDate>Mon, 24 Nov 2008 12:15:59 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=632#comment-1379</guid>
		<description>Good article, thank you. I&#039;ll recommend it to the colleagues on my team :-)</description>
		<content:encoded><![CDATA[<p>Good article, thank you. I&#8217;ll recommend it to the colleagues on my team :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

