<?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/" version="2.0">
<channel>
	<title>Comments for Musings of a Software Development Manager</title>
	
	<link>http://edgibbs.com</link>
	<description>Lessons from managing developers</description>
	<lastBuildDate>Sat, 19 Jun 2010 17:44:45 -0700</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/CommentsForMusingsOfASoftwareDevelopmentManager" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="commentsformusingsofasoftwaredevelopmentmanager" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Comment on Second Wave of SOA by Bryan Green</title>
		<link>http://edgibbs.com/2010/06/16/second-wave-of-soa/comment-page-1/#comment-129755</link>
		<dc:creator>Bryan Green</dc:creator>
		<pubDate>Sat, 19 Jun 2010 17:44:45 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=848#comment-129755</guid>
		<description>Interesting notion -- and here I thought SOA was played out. I'll watch and see with you whether SOA is the next big thing for the middle adopters.</description>
		<content:encoded><![CDATA[<p>Interesting notion &#8212; and here I thought SOA was played out. I&#8217;ll watch and see with you whether SOA is the next big thing for the middle adopters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JUnit 4 with Hamcrest Examples by Sindy Seyb</title>
		<link>http://edgibbs.com/2010/05/23/junit-4-with-hamcrest-examples/comment-page-1/#comment-129752</link>
		<dc:creator>Sindy Seyb</dc:creator>
		<pubDate>Sun, 06 Jun 2010 09:18:24 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=842#comment-129752</guid>
		<description>We all know he's not a real person, he's one of those employees companies make up so the public think they're warm and friendly.</description>
		<content:encoded><![CDATA[<p>We all know he&#8217;s not a real person, he&#8217;s one of those employees companies make up so the public think they&#8217;re warm and friendly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on An Open Letter to Helpdesk Managers on Developer Admin Access by John Fuex</title>
		<link>http://edgibbs.com/2010/01/01/an-open-letter-to-helpdesk-managers-on-developer-admin-access/comment-page-1/#comment-129470</link>
		<dc:creator>John Fuex</dc:creator>
		<pubDate>Sat, 06 Mar 2010 01:52:27 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=780#comment-129470</guid>
		<description>I've been there too, but in just about every case was able to negotiate an exception to the policy for developers. The argument that works best is:
"We build software and the associated deployment packages. To build and test that software run an installer for it as much as a few dozen times in a single day. Would you be willing to provide a dedicated help desk person for our department so we can keep productivity up?"

A similar issue I usually have to wrangle with IT over is the ability for developers to temporarily disable on-access virus scanning or exclude certain folders. It is absolutely critical when doing performance analysis and trying to get a repeatable result.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been there too, but in just about every case was able to negotiate an exception to the policy for developers. The argument that works best is:<br />
&#8220;We build software and the associated deployment packages. To build and test that software run an installer for it as much as a few dozen times in a single day. Would you be willing to provide a dedicated help desk person for our department so we can keep productivity up?&#8221;</p>
<p>A similar issue I usually have to wrangle with IT over is the ability for developers to temporarily disable on-access virus scanning or exclude certain folders. It is absolutely critical when doing performance analysis and trying to get a repeatable result.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Configuration problems with Ruby’s XmlSimple by Administrator</title>
		<link>http://edgibbs.com/2006/05/28/configuration-problems-with-rubys-xmlsimple/comment-page-1/#comment-129464</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Wed, 17 Feb 2010 23:19:53 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=362#comment-129464</guid>
		<description>Yeah, that was a editor typo.  I actually used:

&lt;code&gt;sudo gem install xml-simple&lt;/code&gt;

Thanks for the catch.</description>
		<content:encoded><![CDATA[<p>Yeah, that was a editor typo.  I actually used:</p>
<div class="codecolorer-container text vibrant" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><table cellspacing="0" cellpadding="0"><tbody><tr><td style="padding:5px;text-align:center;color:#888888;background-color:#EEEEEE;border-right: 1px solid #9F9F9F;font: normal 12px/1.4em Monaco, Lucida Console, monospace;"><div>1<br /></div></td><td><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">sudo gem install xml-simple</div></td></tr></tbody></table></div>
<p>Thanks for the catch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Configuration problems with Ruby’s XmlSimple by Bala</title>
		<link>http://edgibbs.com/2006/05/28/configuration-problems-with-rubys-xmlsimple/comment-page-1/#comment-129463</link>
		<dc:creator>Bala</dc:creator>
		<pubDate>Mon, 15 Feb 2010 10:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=362#comment-129463</guid>
		<description>Wrong:

# sudo gem gem install xml-simple

Correct:
sudo gem install xml-simple</description>
		<content:encoded><![CDATA[<p>Wrong:</p>
<p># sudo gem gem install xml-simple</p>
<p>Correct:<br />
sudo gem install xml-simple</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Developer Expectations by Ed Gibbs</title>
		<link>http://edgibbs.com/2010/01/04/developer-expectations/comment-page-1/#comment-129437</link>
		<dc:creator>Ed Gibbs</dc:creator>
		<pubDate>Sun, 10 Jan 2010 02:36:34 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=788#comment-129437</guid>
		<description>Not a bad idea, but I've lately been trying to figure out how useful trending is with bug trackers.  I can't think of a time where I used them for trending other than to show a general pattern on our TDD projects that we saw a very noticeable decrease in defects.  Still the danger there is you can game bug tracking very easily.  I've always used them, but in an Agile context you can often just track them on a card and leave off the official defect tracker.</description>
		<content:encoded><![CDATA[<p>Not a bad idea, but I&#8217;ve lately been trying to figure out how useful trending is with bug trackers.  I can&#8217;t think of a time where I used them for trending other than to show a general pattern on our TDD projects that we saw a very noticeable decrease in defects.  Still the danger there is you can game bug tracking very easily.  I&#8217;ve always used them, but in an Agile context you can often just track them on a card and leave off the official defect tracker.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Faulty Hopes for UI Testing Tools by Ed Gibbs</title>
		<link>http://edgibbs.com/2010/01/05/faulty-hopes-for-ui-testing-tools/comment-page-1/#comment-129436</link>
		<dc:creator>Ed Gibbs</dc:creator>
		<pubDate>Sun, 10 Jan 2010 02:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=790#comment-129436</guid>
		<description>Hope NYC isn't too cold this time of year.  Anyway your right about Cucumber, but then Cucumber is giving you BDD style tests and avoiding the UI again like FIT and others.  I think using something like Selenium for has to be done for now when you're developing javascript heavy front-ends.  The difficult part is if you setup an extensive test suite you suffer from brittleness in these sorts of tests.  So I'm pretty much on the same page with your approach.</description>
		<content:encoded><![CDATA[<p>Hope NYC isn&#8217;t too cold this time of year.  Anyway your right about Cucumber, but then Cucumber is giving you BDD style tests and avoiding the UI again like FIT and others.  I think using something like Selenium for has to be done for now when you&#8217;re developing javascript heavy front-ends.  The difficult part is if you setup an extensive test suite you suffer from brittleness in these sorts of tests.  So I&#8217;m pretty much on the same page with your approach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Faulty Hopes for UI Testing Tools by Luke Melia</title>
		<link>http://edgibbs.com/2010/01/05/faulty-hopes-for-ui-testing-tools/comment-page-1/#comment-129435</link>
		<dc:creator>Luke Melia</dc:creator>
		<pubDate>Thu, 07 Jan 2010 18:51:33 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=790#comment-129435</guid>
		<description>A couple of thoughts, Ed. Cucumber is getting a lot of adoption in the Ruby world. It's my favorite tool bar none for acceptance tests. We use primarily to drive Rails integration tests, but also have it driving a growing Selenium suite since we have a decent amount of javascript-heavy functionality on Weplay. You and Michael are right that these tests are more fragile than tests that skip the UI, but some of this functionality has to be tested, IMO.

Cheers from NYC,
Luke</description>
		<content:encoded><![CDATA[<p>A couple of thoughts, Ed. Cucumber is getting a lot of adoption in the Ruby world. It&#8217;s my favorite tool bar none for acceptance tests. We use primarily to drive Rails integration tests, but also have it driving a growing Selenium suite since we have a decent amount of javascript-heavy functionality on Weplay. You and Michael are right that these tests are more fragile than tests that skip the UI, but some of this functionality has to be tested, IMO.</p>
<p>Cheers from NYC,<br />
Luke</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Developer Expectations by Gavin</title>
		<link>http://edgibbs.com/2010/01/04/developer-expectations/comment-page-1/#comment-129431</link>
		<dc:creator>Gavin</dc:creator>
		<pubDate>Wed, 06 Jan 2010 16:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=788#comment-129431</guid>
		<description>Pretty good list. I would add something about the bug backlog as well - perhaps a trending metric.</description>
		<content:encoded><![CDATA[<p>Pretty good list. I would add something about the bug backlog as well &#8211; perhaps a trending metric.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on An Open Letter to Helpdesk Managers on Developer Admin Access by Ed Gibbs</title>
		<link>http://edgibbs.com/2010/01/01/an-open-letter-to-helpdesk-managers-on-developer-admin-access/comment-page-1/#comment-129424</link>
		<dc:creator>Ed Gibbs</dc:creator>
		<pubDate>Sun, 03 Jan 2010 17:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=780#comment-129424</guid>
		<description>I completely agree that QA/Testers have it much worse.  I always won the argument with the help desk for developers.  I often weighed in with the QA managers to get testers the same admin access and was roundly turned down including by CIOs.  The assumption that testers aren't very technical is very pervasive in the industry.  I did manage a small group of testers for 6 months and I managed to get them admin access by simply pretending they were developers.  

I hope this is getting better for QA, but I fear it isn't.</description>
		<content:encoded><![CDATA[<p>I completely agree that QA/Testers have it much worse.  I always won the argument with the help desk for developers.  I often weighed in with the QA managers to get testers the same admin access and was roundly turned down including by CIOs.  The assumption that testers aren&#8217;t very technical is very pervasive in the industry.  I did manage a small group of testers for 6 months and I managed to get them admin access by simply pretending they were developers.  </p>
<p>I hope this is getting better for QA, but I fear it isn&#8217;t.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
