<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/rss2full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><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" version="2.0">
<channel>
	<title>Comments for Musings of a Software Development Manager</title>
	
	<link>http://edgibbs.com</link>
	<description>Rants on running a team of java developers</description>
	<pubDate>Fri, 21 Nov 2008 05:29:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/CommentsForMusingsOfASoftwareDevelopmentManager" type="application/rss+xml" /><item>
		<title>Comment on Story Points Estimating by Ian Suttle</title>
		<link>http://edgibbs.com/2006/03/11/story-points-estimating/#comment-128788</link>
		<dc:creator>Ian Suttle</dc:creator>
		<pubDate>Fri, 21 Nov 2008 05:20:46 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=292#comment-128788</guid>
		<description>I really like the "relative" part of story points.  We're looking to add story points as a tool to reach a good understanding of velocity so we can forecast release completion timing.  If we were to use days it would be so odd to say "we have a velocity of 12 days of work" over a 10 day iteration for instance.

I've posted on &lt;a href="http://iansuttle.com/blog/post/Betting-on-Story-Points.aspx" rel="nofollow"&gt;story points&lt;/a&gt; with a bit more general thought behind it if interested.</description>
		<content:encoded><![CDATA[<p>I really like the &#8220;relative&#8221; part of story points.  We&#8217;re looking to add story points as a tool to reach a good understanding of velocity so we can forecast release completion timing.  If we were to use days it would be so odd to say &#8220;we have a velocity of 12 days of work&#8221; over a 10 day iteration for instance.</p>
<p>I&#8217;ve posted on <a href="http://iansuttle.com/blog/post/Betting-on-Story-Points.aspx" rel="nofollow">story points</a> with a bit more general thought behind it if interested.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on C# Coding Standards by Ed Gibbs</title>
		<link>http://edgibbs.com/2008/11/02/c-coding-standards/#comment-128783</link>
		<dc:creator>Ed Gibbs</dc:creator>
		<pubDate>Thu, 06 Nov 2008 14:08:37 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=669#comment-128783</guid>
		<description>Thanks for the suggestions.  And a little extra background, I've been asked to help with an effort in another department to switch their staff to .NET.  A coding standard is just a small step in setting them off on the right path.  I'd rather we didn't add another technology to our stack, but apparently that train had already left the station.</description>
		<content:encoded><![CDATA[<p>Thanks for the suggestions.  And a little extra background, I&#8217;ve been asked to help with an effort in another department to switch their staff to .NET.  A coding standard is just a small step in setting them off on the right path.  I&#8217;d rather we didn&#8217;t add another technology to our stack, but apparently that train had already left the station.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on C# Coding Standards by Damon Zirkler</title>
		<link>http://edgibbs.com/2008/11/02/c-coding-standards/#comment-128782</link>
		<dc:creator>Damon Zirkler</dc:creator>
		<pubDate>Mon, 03 Nov 2008 16:14:23 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=669#comment-128782</guid>
		<description>We based our style guide on Lance Hunt's C# style guide, found here: http://weblogs.asp.net/lhunt/pages/CSharp-Coding-Standards-document.aspx</description>
		<content:encoded><![CDATA[<p>We based our style guide on Lance Hunt&#8217;s C# style guide, found here: <a href="http://weblogs.asp.net/lhunt/pages/CSharp-Coding-Standards-document.aspx" rel="nofollow">http://weblogs.asp.net/lhunt/pages/CSharp-Coding-Standards-document.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on C# Coding Standards by brad</title>
		<link>http://edgibbs.com/2008/11/02/c-coding-standards/#comment-128781</link>
		<dc:creator>brad</dc:creator>
		<pubDate>Mon, 03 Nov 2008 06:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=669#comment-128781</guid>
		<description>If you are looking around for an arbitrary set of rules to follow, you are focusing on the wrong thing and are setting your self up for a series of pointless rule-based victories on the road to failure.</description>
		<content:encoded><![CDATA[<p>If you are looking around for an arbitrary set of rules to follow, you are focusing on the wrong thing and are setting your self up for a series of pointless rule-based victories on the road to failure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on C# Coding Standards by Rob Gibbens</title>
		<link>http://edgibbs.com/2008/11/02/c-coding-standards/#comment-128779</link>
		<dc:creator>Rob Gibbens</dc:creator>
		<pubDate>Mon, 03 Nov 2008 04:58:26 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/?p=669#comment-128779</guid>
		<description>Actually, there is a comprehensive set of standards, called the "Framework Design Guidelines".  The book was just released in it's second edition (485 pages I believe).  The rules defined there are also the rules codified in the static analysis tool inside Visual Studio.  They are available online also...just search for ".net framework design guidelines".</description>
		<content:encoded><![CDATA[<p>Actually, there is a comprehensive set of standards, called the &#8220;Framework Design Guidelines&#8221;.  The book was just released in it&#8217;s second edition (485 pages I believe).  The rules defined there are also the rules codified in the static analysis tool inside Visual Studio.  They are available online also&#8230;just search for &#8220;.net framework design guidelines&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sometimes You Want the SysAdmin to Say No by Pawel Brodzinski</title>
		<link>http://edgibbs.com/2008/09/08/sometimes-you-want-the-sysadmin-to-say-no/#comment-128767</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Mon, 29 Sep 2008 21:20:18 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/2008/09/08/sometimes-you-want-the-sysadmin-to-say-no/#comment-128767</guid>
		<description>Most of the time developers should be kept off the production. However I understand to some point Shaun's concerns. When you start forbidding something to people and egos start playing role chances are good you'll invite antagonisms to the team.

Anyway, you shouldn't apply any rule thoughtlessly. Suppose you're a vendor of a system which is a part of core network of mobile operator. Now, you have an emergency situation since one fourth of calls are dropped. You won't block access to production to anyone who's able to fix the issue and do it fast. Even if she's a secretary. By the way the example isn't made up. OK, issue was fixed by the secretary but by a developer.

We chose to go for a compromise. We limited access to production anvironments to most of developers. Only a lead developer of a project can enter the production. Since they're experienced people it works well for now.</description>
		<content:encoded><![CDATA[<p>Most of the time developers should be kept off the production. However I understand to some point Shaun&#8217;s concerns. When you start forbidding something to people and egos start playing role chances are good you&#8217;ll invite antagonisms to the team.</p>
<p>Anyway, you shouldn&#8217;t apply any rule thoughtlessly. Suppose you&#8217;re a vendor of a system which is a part of core network of mobile operator. Now, you have an emergency situation since one fourth of calls are dropped. You won&#8217;t block access to production to anyone who&#8217;s able to fix the issue and do it fast. Even if she&#8217;s a secretary. By the way the example isn&#8217;t made up. OK, issue was fixed by the secretary but by a developer.</p>
<p>We chose to go for a compromise. We limited access to production anvironments to most of developers. Only a lead developer of a project can enter the production. Since they&#8217;re experienced people it works well for now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Laptops In Meetings by 303 Insanely Interesting Links From 2007 -- Jarkko Laine - Insanely interested</title>
		<link>http://edgibbs.com/2007/09/05/laptops-in-meetings/#comment-128764</link>
		<dc:creator>303 Insanely Interesting Links From 2007 -- Jarkko Laine - Insanely interested</dc:creator>
		<pubDate>Tue, 23 Sep 2008 10:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/2007/09/05/laptops-in-meetings/#comment-128764</guid>
		<description>[...] Laptops In Meetings, Musings of a Software Development Manager [...]</description>
		<content:encoded><![CDATA[<p>[...] Laptops In Meetings, Musings of a Software Development Manager [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crisp Meetings by Recent Links Tagged With "cio" - JabberTags</title>
		<link>http://edgibbs.com/2008/08/28/crisp-meetings/#comment-128761</link>
		<dc:creator>Recent Links Tagged With "cio" - JabberTags</dc:creator>
		<pubDate>Fri, 12 Sep 2008 09:04:47 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/2008/08/28/crisp-meetings/#comment-128761</guid>
		<description>[...] public links &gt;&gt; cio   Gmail Outage Outrage Saved by terminal on Fri 12-9-2008   Crisp Meetings Saved by apan2713 on Thu 11-9-2008   RadPharm Appoints new CIO Saved by snize on Sat 06-9-2008   [...]</description>
		<content:encoded><![CDATA[<p>[...] public links &gt;&gt; cio   Gmail Outage Outrage Saved by terminal on Fri 12-9-2008   Crisp Meetings Saved by apan2713 on Thu 11-9-2008   RadPharm Appoints new CIO Saved by snize on Sat 06-9-2008   [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Screencast and Comic Documentation by Ed Gibbs</title>
		<link>http://edgibbs.com/2008/09/09/screencast-and-comic-documentation/#comment-128760</link>
		<dc:creator>Ed Gibbs</dc:creator>
		<pubDate>Thu, 11 Sep 2008 03:12:16 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/2008/09/09/screencast-and-comic-documentation/#comment-128760</guid>
		<description>No problem.  Peepcode is a great resource.</description>
		<content:encoded><![CDATA[<p>No problem.  Peepcode is a great resource.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Screencast and Comic Documentation by Geoffrey Grosenbach</title>
		<link>http://edgibbs.com/2008/09/09/screencast-and-comic-documentation/#comment-128759</link>
		<dc:creator>Geoffrey Grosenbach</dc:creator>
		<pubDate>Wed, 10 Sep 2008 14:57:52 +0000</pubDate>
		<guid isPermaLink="false">http://edgibbs.com/2008/09/09/screencast-and-comic-documentation/#comment-128759</guid>
		<description>Thanks for the props! The ScreenFlow application on the Mac is also a useful piece of software for short screencasts. The PeepCode screencast will soon be updated to mention it.

  http://www.flip4mac.com/screenflow.htm</description>
		<content:encoded><![CDATA[<p>Thanks for the props! The ScreenFlow application on the Mac is also a useful piece of software for short screencasts. The PeepCode screencast will soon be updated to mention it.</p>
<p>  <a href="http://www.flip4mac.com/screenflow.htm" rel="nofollow">http://www.flip4mac.com/screenflow.htm</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
