<?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: How To Be More Productive</title>
	<atom:link href="http://www.fictitiousnonsense.com/archives/49/feed" rel="self" type="application/rss+xml" />
	<link>http://www.fictitiousnonsense.com/archives/49</link>
	<description>&#38; Wasted Ink</description>
	<lastBuildDate>Thu, 17 Feb 2011 15:59:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Emil</title>
		<link>http://www.fictitiousnonsense.com/archives/49/comment-page-1#comment-128</link>
		<dc:creator>Emil</dc:creator>
		<pubDate>Thu, 17 Feb 2011 15:59:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.fictitiousnonsense.com/?p=49#comment-128</guid>
		<description>Just found this post when googling around for a way to emulate config specs in git.. and the reason for this being that git is completely useless when it comes to most tasks that involve more than one tiny team of developers. I&#039;ve been using ClearCase at the last three work places, but here it&#039;s git, and I waste pretty much the same amount of time you claim to have lost to CC&#039;s &quot;problems&quot; just crying and banging my head against the wall trying to figure out just why git has to be so painfully inept.

Anyway, to each his own I guess, but you should probably work on your argumentation if you really want to get rid of CC since what toomyem said holds true: the problems you had existed between the keyboard and the chair, not within CC :P</description>
		<content:encoded><![CDATA[<p>Just found this post when googling around for a way to emulate config specs in git.. and the reason for this being that git is completely useless when it comes to most tasks that involve more than one tiny team of developers. I&#8217;ve been using ClearCase at the last three work places, but here it&#8217;s git, and I waste pretty much the same amount of time you claim to have lost to CC&#8217;s &#8220;problems&#8221; just crying and banging my head against the wall trying to figure out just why git has to be so painfully inept.</p>
<p>Anyway, to each his own I guess, but you should probably work on your argumentation if you really want to get rid of CC since what toomyem said holds true: the problems you had existed between the keyboard and the chair, not within CC :P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: toomyem</title>
		<link>http://www.fictitiousnonsense.com/archives/49/comment-page-1#comment-89</link>
		<dc:creator>toomyem</dc:creator>
		<pubDate>Fri, 18 Dec 2009 00:40:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.fictitiousnonsense.com/?p=49#comment-89</guid>
		<description>Don&#039;t blame CC for your lack of knowledge. Missing /main/0 is your fault. CC can&#039;t checkout element if it is not visible by any rule. I&#039;m playing with CC for over 8 years and find the config-spec-idea very convenient and powerful.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t blame CC for your lack of knowledge. Missing /main/0 is your fault. CC can&#8217;t checkout element if it is not visible by any rule. I&#8217;m playing with CC for over 8 years and find the config-spec-idea very convenient and powerful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles O'Farrell</title>
		<link>http://www.fictitiousnonsense.com/archives/49/comment-page-1#comment-79</link>
		<dc:creator>Charles O'Farrell</dc:creator>
		<pubDate>Sun, 26 Jul 2009 13:47:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.fictitiousnonsense.com/?p=49#comment-79</guid>
		<description>I feel your pain John. I too have to suffer Clearcase at work.

If its of any interest I&#039;ve written a Git/Clearcase bridge which may alleviate (some) of the pain.

http://blog.charleso.org/2008/10/clearcase-for-git.html

The biggest problem I&#039;m having now is convincing the person in charge of our SCM the benefits of using something like Git. His argument against things like speed is that: in the end it&#039;s not going to change how fast you produce quality software. While I can&#039;t fault that argument specifically, it doesn&#039;t take into consideration an intangible thing like developer happiness. I think part of the problem is that he&#039;s not a developer and so he doesn&#039;t have to deal with Clearcase on a day-by-day, minute-by-minute basis. *sigh*</description>
		<content:encoded><![CDATA[<p>I feel your pain John. I too have to suffer Clearcase at work.</p>
<p>If its of any interest I&#8217;ve written a Git/Clearcase bridge which may alleviate (some) of the pain.</p>
<p><a href="http://blog.charleso.org/2008/10/clearcase-for-git.html" rel="nofollow">http://blog.charleso.org/2008/10/clearcase-for-git.html</a></p>
<p>The biggest problem I&#8217;m having now is convincing the person in charge of our SCM the benefits of using something like Git. His argument against things like speed is that: in the end it&#8217;s not going to change how fast you produce quality software. While I can&#8217;t fault that argument specifically, it doesn&#8217;t take into consideration an intangible thing like developer happiness. I think part of the problem is that he&#8217;s not a developer and so he doesn&#8217;t have to deal with Clearcase on a day-by-day, minute-by-minute basis. *sigh*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KeHoeff</title>
		<link>http://www.fictitiousnonsense.com/archives/49/comment-page-1#comment-54</link>
		<dc:creator>KeHoeff</dc:creator>
		<pubDate>Fri, 29 May 2009 01:35:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.fictitiousnonsense.com/?p=49#comment-54</guid>
		<description>hey this is a very interesting article!</description>
		<content:encoded><![CDATA[<p>hey this is a very interesting article!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

