<?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: Form follows function (unless you&#8217;ve got a knighthood)</title>
	<atom:link href="http://blog.pigsaw.org/permalink/2006/02/07/289/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.pigsaw.org/permalink/2006/02/07/289</link>
	<description>All the pig that&#039;s fit to saw</description>
	<lastBuildDate>Mon, 12 Dec 2011 17:48:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Nik</title>
		<link>http://blog.pigsaw.org/permalink/2006/02/07/289/comment-page-1#comment-1377</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Wed, 08 Feb 2006 19:28:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pigsaw.org/permalink/2006/02/07/289#comment-1377</guid>
		<description>I realise this is controversial. Generally I&#039;d say the idea of developers doing things that their peers are unaware of is very bad, and that means private offices are (in general) very bad. This certainly does &lt;em&gt;not&lt;/em&gt; mean that developers should never be allowed to work in a quiet place. It &lt;em&gt;does&lt;/em&gt; mean that &quot;lots of people all working on different projects and with different skills&quot; is bad position to be in. It suggests too many projects and (if everyone is a specialist in a different area) few people to seek advice from. Your multi-disciplined team scenario is ideal, even if you expect people to have different levels of expertise in different areas.

Getting the product out the door is only half the problem. Keeping it maintained is the other half. And that&#039;s when you need a good spread of knowledge.</description>
		<content:encoded><![CDATA[<p>I realise this is controversial. Generally I&#8217;d say the idea of developers doing things that their peers are unaware of is very bad, and that means private offices are (in general) very bad. This certainly does <em>not</em> mean that developers should never be allowed to work in a quiet place. It <em>does</em> mean that &#8220;lots of people all working on different projects and with different skills&#8221; is bad position to be in. It suggests too many projects and (if everyone is a specialist in a different area) few people to seek advice from. Your multi-disciplined team scenario is ideal, even if you expect people to have different levels of expertise in different areas.</p>
<p>Getting the product out the door is only half the problem. Keeping it maintained is the other half. And that&#8217;s when you need a good spread of knowledge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MC</title>
		<link>http://blog.pigsaw.org/permalink/2006/02/07/289/comment-page-1#comment-1376</link>
		<dc:creator>MC</dc:creator>
		<pubDate>Wed, 08 Feb 2006 12:22:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pigsaw.org/permalink/2006/02/07/289#comment-1376</guid>
		<description>Well, that is a &lt;a HREF=&quot;http://discuss.joelonsoftware.com/default.asp?joel.3.263875.32#discussTopic264326/&quot; rel=&quot;nofollow&quot;&gt;   heavily&lt;/a&gt; &lt;a HREF=&quot;http://www.joelonsoftware.com/items/2005/10/16.html/&quot; rel=&quot;nofollow&quot;&gt;debated&lt;/a&gt; subject over on &lt;a HREF=&quot;http://www.joelonsoftware.com/articles/fog0000000068.html/&quot; rel=&quot;nofollow&quot;&gt;Joel&#039;s  site.&lt;/a&gt; I expect it depends on what kind of work you are doing, if you are all working on the same project and in the same discipline or if its a multi-discipline &quot;team&quot;. From experience, lots of people all working on different projects and with different skills don&#039;t make the best environment for the software guys...

</description>
		<content:encoded><![CDATA[<p>Well, that is a <a HREF="http://discuss.joelonsoftware.com/default.asp?joel.3.263875.32#discussTopic264326/" rel="nofollow">   heavily</a> <a HREF="http://www.joelonsoftware.com/items/2005/10/16.html/" rel="nofollow">debated</a> subject over on <a HREF="http://www.joelonsoftware.com/articles/fog0000000068.html/" rel="nofollow">Joel&#8217;s  site.</a> I expect it depends on what kind of work you are doing, if you are all working on the same project and in the same discipline or if its a multi-discipline &#8220;team&#8221;. From experience, lots of people all working on different projects and with different skills don&#8217;t make the best environment for the software guys&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nik</title>
		<link>http://blog.pigsaw.org/permalink/2006/02/07/289/comment-page-1#comment-1374</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Wed, 08 Feb 2006 09:00:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pigsaw.org/permalink/2006/02/07/289#comment-1374</guid>
		<description>Good article. I remember reading it at the time and I thought then the same as I think now: it&#039;s all terrific but I strongly disagree with requirement 1: &quot;Private offices with doors that close were absolutely required and not open to negotiation.&quot;

Or to be more specific, while it&#039;s good to have some of those for one-off uses I think it&#039;s very bad for them to be the primary home or development space of developers. For me, so much value is obtained from collaboration -- even casual overheard remarks -- that developers locked away in silence flashes big red alarm lights immediately.</description>
		<content:encoded><![CDATA[<p>Good article. I remember reading it at the time and I thought then the same as I think now: it&#8217;s all terrific but I strongly disagree with requirement 1: &#8220;Private offices with doors that close were absolutely required and not open to negotiation.&#8221;</p>
<p>Or to be more specific, while it&#8217;s good to have some of those for one-off uses I think it&#8217;s very bad for them to be the primary home or development space of developers. For me, so much value is obtained from collaboration &#8212; even casual overheard remarks &#8212; that developers locked away in silence flashes big red alarm lights immediately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MC</title>
		<link>http://blog.pigsaw.org/permalink/2006/02/07/289/comment-page-1#comment-1373</link>
		<dc:creator>MC</dc:creator>
		<pubDate>Tue, 07 Feb 2006 15:35:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pigsaw.org/permalink/2006/02/07/289#comment-1373</guid>
		<description>Maybe this country needs a &lt;a HREF=&quot;http://www.joelonsoftware.com/articles/BionicOffice.html&quot; rel=&quot;nofollow&quot;&gt;Roy Leone&lt;/a&gt; to do things as the customer needs them.</description>
		<content:encoded><![CDATA[<p>Maybe this country needs a <a HREF="http://www.joelonsoftware.com/articles/BionicOffice.html" rel="nofollow">Roy Leone</a> to do things as the customer needs them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

