<?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 for niksilver.com</title>
	<atom:link href="http://niksilver.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://niksilver.com</link>
	<description>Mostly about the management of software development</description>
	<lastBuildDate>Wed, 27 Jan 2010 09:48:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Discovering JavaFX with the Guardian Open Platform by William</title>
		<link>http://niksilver.com/2009/08/31/discovering-javafx-with-the-guardian-open-platform/comment-page-1/#comment-33992</link>
		<dc:creator>William</dc:creator>
		<pubDate>Wed, 27 Jan 2010 09:48:25 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=499#comment-33992</guid>
		<description>Hmm, I tried it on a Mac, and it wasn&#039;t so bad.  I did have to click two OK buttons to install JavaFX (which took under ten seconds) -- but if I didn&#039;t have Flash installed, I&#039;d get the equivalent prompts.</description>
		<content:encoded><![CDATA[<p>Hmm, I tried it on a Mac, and it wasn&#8217;t so bad.  I did have to click two OK buttons to install JavaFX (which took under ten seconds) &#8212; but if I didn&#8217;t have Flash installed, I&#8217;d get the equivalent prompts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on An ABC of R2: J is for JFDI by Nik</title>
		<link>http://niksilver.com/2008/12/01/an-abc-of-r2-j-is-for-jfdi/comment-page-1/#comment-33987</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Wed, 11 Nov 2009 17:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=198#comment-33987</guid>
		<description>Hi Paul. We do still have a team dedicated to quick turnaround work (including bugfixing), but to be honest JFDI was never their official name outside the team.</description>
		<content:encoded><![CDATA[<p>Hi Paul. We do still have a team dedicated to quick turnaround work (including bugfixing), but to be honest JFDI was never their official name outside the team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on An ABC of R2: J is for JFDI by Paul Lomax</title>
		<link>http://niksilver.com/2008/12/01/an-abc-of-r2-j-is-for-jfdi/comment-page-1/#comment-33986</link>
		<dc:creator>Paul Lomax</dc:creator>
		<pubDate>Wed, 11 Nov 2009 16:36:40 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=198#comment-33986</guid>
		<description>Hi Nick,

I forgot to ask you last time I was at King&#039;s Place - do you still have a &quot;JFDI&quot; team? And do you still call them that?? :-)

Cheers

Paul</description>
		<content:encoded><![CDATA[<p>Hi Nick,</p>
<p>I forgot to ask you last time I was at King&#8217;s Place &#8211; do you still have a &#8220;JFDI&#8221; team? And do you still call them that?? <img src='http://niksilver.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Cheers</p>
<p>Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Discovering JavaFX with the Guardian Open Platform by zammbi</title>
		<link>http://niksilver.com/2009/08/31/discovering-javafx-with-the-guardian-open-platform/comment-page-1/#comment-33983</link>
		<dc:creator>zammbi</dc:creator>
		<pubDate>Wed, 07 Oct 2009 08:52:23 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=499#comment-33983</guid>
		<description>10^80 atoms in the universe :)

Hopefully Java 7 helps solve some of the problems you have listed.</description>
		<content:encoded><![CDATA[<p>10^80 atoms in the universe <img src='http://niksilver.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Hopefully Java 7 helps solve some of the problems you have listed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A few things I know about lean by Nik</title>
		<link>http://niksilver.com/2009/09/10/a-few-things-i-know-about-lean/comment-page-1/#comment-33982</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Fri, 25 Sep 2009 17:18:27 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=549#comment-33982</guid>
		<description>Hi Rupert. Having oversight from beginning to end is part of being lean, although just saying the developer should put it live doesn&#039;t make it lean of course. Just as important (possibly more so) is the team working together, and continually putting the features live. If the developer happens to be the last person in the chain that&#039;s fine; in the lean world that go-live action should be a continuously repeating step that&#039;s part of a flow.</description>
		<content:encoded><![CDATA[<p>Hi Rupert. Having oversight from beginning to end is part of being lean, although just saying the developer should put it live doesn&#8217;t make it lean of course. Just as important (possibly more so) is the team working together, and continually putting the features live. If the developer happens to be the last person in the chain that&#8217;s fine; in the lean world that go-live action should be a continuously repeating step that&#8217;s part of a flow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A few things I know about lean by Rupert</title>
		<link>http://niksilver.com/2009/09/10/a-few-things-i-know-about-lean/comment-page-1/#comment-33977</link>
		<dc:creator>Rupert</dc:creator>
		<pubDate>Wed, 23 Sep 2009 19:50:33 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=549#comment-33977</guid>
		<description>Interesting stuff. The ideas surely apply beyond the actual production of the software to the processes involved in moving it into production. The way we work usually results in the developer being the one responsible for putting code live, which has caused a few raised eyebrows over the years, but does have a number of benefits, notably that if there are problems the developer is probably the person best placed to diagnose and fix them. This would seem to resonate with the ideas you&#039;ve outlined in this post.</description>
		<content:encoded><![CDATA[<p>Interesting stuff. The ideas surely apply beyond the actual production of the software to the processes involved in moving it into production. The way we work usually results in the developer being the one responsible for putting code live, which has caused a few raised eyebrows over the years, but does have a number of benefits, notably that if there are problems the developer is probably the person best placed to diagnose and fix them. This would seem to resonate with the ideas you&#8217;ve outlined in this post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A health warning to followers of the Knight News Challenge by Nik</title>
		<link>http://niksilver.com/2009/09/14/a-health-warning-to-followers-of-the-knight-news-challenge/comment-page-1/#comment-33974</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Tue, 15 Sep 2009 08:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=565#comment-33974</guid>
		<description>Hi Ryan. Thanks for the further insight. I do realise it&#039;s impossible to condense all the subtleties down into a few soundbites. But then it&#039;s also always fascinating to hear many of the details of the kind you outline above, especially when it&#039;s on a project which has become public, because then an observer can compare their assumptions with the reality.</description>
		<content:encoded><![CDATA[<p>Hi Ryan. Thanks for the further insight. I do realise it&#8217;s impossible to condense all the subtleties down into a few soundbites. But then it&#8217;s also always fascinating to hear many of the details of the kind you outline above, especially when it&#8217;s on a project which has become public, because then an observer can compare their assumptions with the reality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A health warning to followers of the Knight News Challenge by Ryan Sholin</title>
		<link>http://niksilver.com/2009/09/14/a-health-warning-to-followers-of-the-knight-news-challenge/comment-page-1/#comment-33973</link>
		<dc:creator>Ryan Sholin</dc:creator>
		<pubDate>Tue, 15 Sep 2009 01:48:58 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=565#comment-33973</guid>
		<description>Hi Nik -- Thanks for the feedback! I&#039;m glad someone stopped and actually read the post instead of just retweeting it. A lot of that going around.

First of all, as in all things on the Web, your mileage may vary. But yes, my list at the Knight News Challenge blog was definitely geared toward entrants into that particular blender of funding and ideas.

In my case, I had some experience working with developers and some experience doing very lightweight development myself. I&#039;m an edge case. But I&#039;ve noticed that a few of my fellow News Challenge winners tend to be edge cases themselves. So that&#039;s the audience I was preaching to in that particular post.

To your points:

1. If you&#039;re on a larger team, congratulations. You either know what you&#039;re doing already, or you have enough padding in your grant to make a few mistakes. That&#039;s good! Fail fast, and move on to the next iteration.

2. You&#039;re absolutely right. In the case of the second version of ReportingOn, I spent somewhere in the neighborhood of 8 hours (over the course of a few meetings) in a room with my development duo, with one of them standing in front of a whiteboard guiding the discussion, figuring out what I had in mind, and all of us having some very vivid conversations about the details. I&#039;ve boiled that down to &quot;telling them what you want&quot; because if you&#039;re not willing to put in the time to make your vision clear to your team, you&#039;re not going to get anything out of the exercise that resembles what you imagined.

But by all means, don&#039;t mistake what I&#039;ve learned from experience as a general prescription! If your mileage doesn&#039;t vary in one way or another, then something&#039;s gone horribly wrong here.</description>
		<content:encoded><![CDATA[<p>Hi Nik &#8212; Thanks for the feedback! I&#8217;m glad someone stopped and actually read the post instead of just retweeting it. A lot of that going around.</p>
<p>First of all, as in all things on the Web, your mileage may vary. But yes, my list at the Knight News Challenge blog was definitely geared toward entrants into that particular blender of funding and ideas.</p>
<p>In my case, I had some experience working with developers and some experience doing very lightweight development myself. I&#8217;m an edge case. But I&#8217;ve noticed that a few of my fellow News Challenge winners tend to be edge cases themselves. So that&#8217;s the audience I was preaching to in that particular post.</p>
<p>To your points:</p>
<p>1. If you&#8217;re on a larger team, congratulations. You either know what you&#8217;re doing already, or you have enough padding in your grant to make a few mistakes. That&#8217;s good! Fail fast, and move on to the next iteration.</p>
<p>2. You&#8217;re absolutely right. In the case of the second version of ReportingOn, I spent somewhere in the neighborhood of 8 hours (over the course of a few meetings) in a room with my development duo, with one of them standing in front of a whiteboard guiding the discussion, figuring out what I had in mind, and all of us having some very vivid conversations about the details. I&#8217;ve boiled that down to &#8220;telling them what you want&#8221; because if you&#8217;re not willing to put in the time to make your vision clear to your team, you&#8217;re not going to get anything out of the exercise that resembles what you imagined.</p>
<p>But by all means, don&#8217;t mistake what I&#8217;ve learned from experience as a general prescription! If your mileage doesn&#8217;t vary in one way or another, then something&#8217;s gone horribly wrong here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A few things I know about lean by Nik</title>
		<link>http://niksilver.com/2009/09/10/a-few-things-i-know-about-lean/comment-page-1/#comment-33972</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Fri, 11 Sep 2009 17:42:51 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=549#comment-33972</guid>
		<description>Thanks for that tip, Richard, I&#039;ll follow it up. The Toyota Way seems to switch between the process of producing individual cars with the process that produced the Prius prototype, and they&#039;re clearly different kinds of things.</description>
		<content:encoded><![CDATA[<p>Thanks for that tip, Richard, I&#8217;ll follow it up. The Toyota Way seems to switch between the process of producing individual cars with the process that produced the Prius prototype, and they&#8217;re clearly different kinds of things.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A few things I know about lean by Richard Lord</title>
		<link>http://niksilver.com/2009/09/10/a-few-things-i-know-about-lean/comment-page-1/#comment-33971</link>
		<dc:creator>Richard Lord</dc:creator>
		<pubDate>Fri, 11 Sep 2009 10:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=549#comment-33971</guid>
		<description>When considering the transition of these principles from manufacturing to software development, it&#039;s well worth checking out the Toyota Product Development System. This is Toyota&#039;s product design process, as opposed to their more famous manufacturing process called the Toyota Production System.</description>
		<content:encoded><![CDATA[<p>When considering the transition of these principles from manufacturing to software development, it&#8217;s well worth checking out the Toyota Product Development System. This is Toyota&#8217;s product design process, as opposed to their more famous manufacturing process called the Toyota Production System.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
