<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
	<title>Comments for From Journeyman to Master</title>
	
	<link>http://www.simonlin.ca</link>
	<description>A site by Simon Lin</description>
	<lastBuildDate>Tue, 24 Jun 2008 17:59:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/CommentsForFromJourneymanToMaster" /><feedburner:info uri="commentsforfromjourneymantomaster" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:browserFriendly></feedburner:browserFriendly><item>
		<title>Comment on Updates from Seattle by Conrad Gustafson</title>
		<link>http://www.simonlin.ca/2008/02/18/updates-from-seattle/comment-page-1/#comment-100</link>
		<dc:creator>Conrad Gustafson</dc:creator>
		<pubDate>Tue, 24 Jun 2008 17:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonlin.ca/2008/02/18/updates-from-seattle/#comment-100</guid>
		<description>&lt;p&gt;Hey Simon!&lt;/p&gt;

&lt;p&gt;It's Conrad from the old PAS days (2005).&lt;/p&gt;

&lt;p&gt;You're in Seattle now?  That's so cool.  I'm just across the water in Victoria.  &lt;/p&gt;

&lt;p&gt;I was wondering if you ever solved the Oracle/Mac OS X problem.  I just bought a MacBook Pro and I thought about taking a crack at it.  Give me a shout -- I'd love to hear about your work.&lt;/p&gt;

&lt;p&gt;PS. Congrats on the baby!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hey Simon!</p>

<p>It&#8217;s Conrad from the old PAS days (2005).</p>

<p>You&#8217;re in Seattle now?  That&#8217;s so cool.  I&#8217;m just across the water in Victoria.  </p>

<p>I was wondering if you ever solved the Oracle/Mac OS X problem.  I just bought a MacBook Pro and I thought about taking a crack at it.  Give me a shout &#8212; I&#8217;d love to hear about your work.</p>

<p>PS. Congrats on the baby!</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Collective Code Ownership – a misused Agile practice by Mark Levison</title>
		<link>http://www.simonlin.ca/2007/07/17/collective-code-ownership-a-misused-agile-practice/comment-page-1/#comment-94</link>
		<dc:creator>Mark Levison</dc:creator>
		<pubDate>Mon, 05 May 2008 01:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonlin.ca/2007/07/17/collective-code-ownership-a-misused-agile-practice/#comment-94</guid>
		<description>&lt;p&gt;It sounds like there has been a misunderstanding somewhere. Collective Code Ownership doesn't say you should all share the same account for the source code control system. &lt;/p&gt;

&lt;p&gt;It says we share ownership of the code and anyone can make a change where ever they think they need it.&lt;/p&gt;

&lt;p&gt;Cheers
Mark Levison&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It sounds like there has been a misunderstanding somewhere. Collective Code Ownership doesn&#8217;t say you should all share the same account for the source code control system. </p>

<p>It says we share ownership of the code and anyone can make a change where ever they think they need it.</p>

<p>Cheers
Mark Levison</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why are we using Ant again? by Jeff Perrin</title>
		<link>http://www.simonlin.ca/2008/04/18/why-are-we-using-ant-again/comment-page-1/#comment-90</link>
		<dc:creator>Jeff Perrin</dc:creator>
		<pubDate>Fri, 18 Apr 2008 14:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonlin.ca/2008/04/18/why-are-we-using-ant-again/#comment-90</guid>
		<description>&lt;p&gt;Stop wasting time with Ruby and mail me an iPhone.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Stop wasting time with Ruby and mail me an iPhone.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Updates from Seattle by simon</title>
		<link>http://www.simonlin.ca/2008/02/18/updates-from-seattle/comment-page-1/#comment-82</link>
		<dc:creator>simon</dc:creator>
		<pubDate>Wed, 20 Feb 2008 06:38:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonlin.ca/2008/02/18/updates-from-seattle/#comment-82</guid>
		<description>&lt;p&gt;Thanks buddy.&lt;/p&gt;

&lt;p&gt;35 minutes of hackysack?  Pretty good exercise, eh?  You can play Guitar Heros if you come here. :-)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks buddy.</p>

<p>35 minutes of hackysack?  Pretty good exercise, eh?  You can play Guitar Heros if you come here. <img src='http://www.simonlin.ca/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Updates from Seattle by Mike Buckley</title>
		<link>http://www.simonlin.ca/2008/02/18/updates-from-seattle/comment-page-1/#comment-81</link>
		<dc:creator>Mike Buckley</dc:creator>
		<pubDate>Tue, 19 Feb 2008 22:41:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonlin.ca/2008/02/18/updates-from-seattle/#comment-81</guid>
		<description>&lt;p&gt;3:40pm
Congratulations Simon! Glad to hear......&lt;/p&gt;

&lt;p&gt;4:15pm
everything is going well in Seattle.&lt;/p&gt;

&lt;p&gt;(Sorry had to go play hackysack =p)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>3:40pm
Congratulations Simon! Glad to hear&#8230;&#8230;</p>

<p>4:15pm
everything is going well in Seattle.</p>

<p>(Sorry had to go play hackysack =p)</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on More about SevenMock by Simon</title>
		<link>http://www.simonlin.ca/2008/01/14/more-about-sevenmock/comment-page-1/#comment-79</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Mon, 28 Jan 2008 07:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonlin.ca/2008/01/15/more-about-sevenmock/#comment-79</guid>
		<description>&lt;p&gt;@James:
I guess I was just not patient enough to read through the tutorial.  I understood SevenMock the moment I read its example.&lt;/p&gt;

&lt;p&gt;@Colin:
I've been writing more tests with SevenMock.  I'll sure post my findings on the Wiki.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@James:
I guess I was just not patient enough to read through the tutorial.  I understood SevenMock the moment I read its example.</p>

<p>@Colin:
I&#8217;ve been writing more tests with SevenMock.  I&#8217;ll sure post my findings on the Wiki.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on More about SevenMock by Colin</title>
		<link>http://www.simonlin.ca/2008/01/14/more-about-sevenmock/comment-page-1/#comment-76</link>
		<dc:creator>Colin</dc:creator>
		<pubDate>Tue, 15 Jan 2008 16:03:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonlin.ca/2008/01/15/more-about-sevenmock/#comment-76</guid>
		<description>&lt;p&gt;Glad to hear that you found SevenMock useful :)&lt;/p&gt;

&lt;p&gt;I'd certainly be interested to know if you or anyone else has thoughts on whether/how SevenMock could be extended. I'm keen to keep it simple, but a couple of ideas that I've been working on are a test recorder and flexible sequencing. &lt;/p&gt;

&lt;p&gt;I'm using the project wiki to push some ideas about:
http://seven-mock.wiki.sourceforge.net/Features+and+Improvements&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Glad to hear that you found SevenMock useful <img src='http://www.simonlin.ca/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>

<p>I&#8217;d certainly be interested to know if you or anyone else has thoughts on whether/how SevenMock could be extended. I&#8217;m keen to keep it simple, but a couple of ideas that I&#8217;ve been working on are a test recorder and flexible sequencing. </p>

<p>I&#8217;m using the project wiki to push some ideas about:
<a href="http://seven-mock.wiki.sourceforge.net/Features+and+Improvements" rel="nofollow">http://seven-mock.wiki.sourceforge.net/Features+and+Improvements</a></p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on More about SevenMock by James</title>
		<link>http://www.simonlin.ca/2008/01/14/more-about-sevenmock/comment-page-1/#comment-75</link>
		<dc:creator>James</dc:creator>
		<pubDate>Tue, 15 Jan 2008 08:20:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonlin.ca/2008/01/15/more-about-sevenmock/#comment-75</guid>
		<description>&lt;p&gt;In jMock you use a parameter Matcher.  Two minutes of reading the cookbook would give you the answer.&lt;/p&gt;

&lt;p&gt;If it sounds as if you have not understood how your persistence layer works.  A value type (like an integer) should always implement equals and hashCode.  An entity should not, and should only be compared by reference. So jMock does the right thing and, by failing the test, is showing you that there is a problem in the code.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>In jMock you use a parameter Matcher.  Two minutes of reading the cookbook would give you the answer.</p>

<p>If it sounds as if you have not understood how your persistence layer works.  A value type (like an integer) should always implement equals and hashCode.  An entity should not, and should only be compared by reference. So jMock does the right thing and, by failing the test, is showing you that there is a problem in the code.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Collective Code Ownership – a misused Agile practice by Vladimir Levin</title>
		<link>http://www.simonlin.ca/2007/07/17/collective-code-ownership-a-misused-agile-practice/comment-page-1/#comment-56</link>
		<dc:creator>Vladimir Levin</dc:creator>
		<pubDate>Fri, 20 Jul 2007 06:52:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonlin.ca/2007/07/17/collective-code-ownership-a-misused-agile-practice/#comment-56</guid>
		<description>&lt;p&gt;In theory pair programming should act as a form of real time code review, so people really should not find it easy to hide their incompetence. On the other hand, if that isn't enough, then I can think of only two solutions. The first is to do some chalk talks in which you highlight problems you've seen in the code and address how best to avoid them. You can also offer to pair with anyone who wants help. Hopefully that's enough because the second solution is much more extreme: If some people are really not able to write code that's up to par, even after you've really tried to help them, then fire them. Maybe I have too much faith in people, but I like to believe that if you help people to learn better ways of doing things, they'll catch on and improve. &lt;/p&gt;

&lt;p&gt;I have to admit that there are areas of PAS where I found myself wondering how so much code was written without anyone really hunkering down and thinking about what needed to be done. Instead there's this mess of kludges that barely holds together, and if you try to fix one part, then something else that was written to balance the first kludge breaks, and so on.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>In theory pair programming should act as a form of real time code review, so people really should not find it easy to hide their incompetence. On the other hand, if that isn&#8217;t enough, then I can think of only two solutions. The first is to do some chalk talks in which you highlight problems you&#8217;ve seen in the code and address how best to avoid them. You can also offer to pair with anyone who wants help. Hopefully that&#8217;s enough because the second solution is much more extreme: If some people are really not able to write code that&#8217;s up to par, even after you&#8217;ve really tried to help them, then fire them. Maybe I have too much faith in people, but I like to believe that if you help people to learn better ways of doing things, they&#8217;ll catch on and improve. </p>

<p>I have to admit that there are areas of PAS where I found myself wondering how so much code was written without anyone really hunkering down and thinking about what needed to be done. Instead there&#8217;s this mess of kludges that barely holds together, and if you try to fix one part, then something else that was written to balance the first kludge breaks, and so on.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Collective Code Ownership – a misused Agile practice by Jeff Perrin</title>
		<link>http://www.simonlin.ca/2007/07/17/collective-code-ownership-a-misused-agile-practice/comment-page-1/#comment-55</link>
		<dc:creator>Jeff Perrin</dc:creator>
		<pubDate>Tue, 17 Jul 2007 14:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonlin.ca/2007/07/17/collective-code-ownership-a-misused-agile-practice/#comment-55</guid>
		<description>&lt;p&gt;Sounds like somebody needs a vaaaacaaation! I admit I hate crappy code, but perhaps my favorite thing in the world (after beer, golf, and babes) is refactoring that code. It can be almost therapeutic, and nothing beats taking a tangled mess of junk and turning it into a thing of pure awesomeness.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Sounds like somebody needs a vaaaacaaation! I admit I hate crappy code, but perhaps my favorite thing in the world (after beer, golf, and babes) is refactoring that code. It can be almost therapeutic, and nothing beats taking a tangled mess of junk and turning it into a thing of pure awesomeness.</p>]]></content:encoded>
	</item>
</channel>
</rss>
