<?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: Concurrent design and development &#8211; a better spin?</title>
	<atom:link href="http://www.kerrybuckley.org/2007/09/26/concurrent-design-and-development-a-better-spin/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kerrybuckley.org/2007/09/26/concurrent-design-and-development-a-better-spin/</link>
	<description>What's the simplest thing that could possibly go wrong?</description>
	<lastBuildDate>Mon, 30 Jan 2012 16:30: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: Kerry</title>
		<link>http://www.kerrybuckley.org/2007/09/26/concurrent-design-and-development-a-better-spin/comment-page-1/#comment-8406</link>
		<dc:creator>Kerry</dc:creator>
		<pubDate>Fri, 05 Oct 2007 10:39:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.kerrybuckley.com/2007/09/26/concurrent-design-and-development-a-better-spin/#comment-8406</guid>
		<description>I take your point to some extent, but I&#039;d argue that many of the problems we have in implementing IT are caused by the de-skilling and devaluing of software development.

In my opinion design and development are two sides of the same coin, and should be separated as little as possible. Trying to increase agility while still treating coding as monkey work is doomed, IMO.

As far as architecture and overall design goes, that&#039;s something that is handled by the team as a whole, guided by the most experienced developer/designer/architects.

See Martin Fowler&#039;s articles &lt;a href=&quot;http://martinfowler.com/articles/designDead.html#id2251106&quot; rel=&quot;nofollow&quot;&gt;Is Design Dead?&lt;/a&gt; and &lt;a href=&quot;http://martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf&quot; rel=&quot;nofollow&quot;&gt;Who Needs an Architect?&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I take your point to some extent, but I&#8217;d argue that many of the problems we have in implementing IT are caused by the de-skilling and devaluing of software development.</p>
<p>In my opinion design and development are two sides of the same coin, and should be separated as little as possible. Trying to increase agility while still treating coding as monkey work is doomed, IMO.</p>
<p>As far as architecture and overall design goes, that&#8217;s something that is handled by the team as a whole, guided by the most experienced developer/designer/architects.</p>
<p>See Martin Fowler&#8217;s articles <a href="http://martinfowler.com/articles/designDead.html#id2251106" rel="nofollow">Is Design Dead?</a> and <a href="http://martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf" rel="nofollow">Who Needs an Architect?</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nik Sargent</title>
		<link>http://www.kerrybuckley.org/2007/09/26/concurrent-design-and-development-a-better-spin/comment-page-1/#comment-8343</link>
		<dc:creator>Nik Sargent</dc:creator>
		<pubDate>Wed, 03 Oct 2007 23:17:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.kerrybuckley.com/2007/09/26/concurrent-design-and-development-a-better-spin/#comment-8343</guid>
		<description>I tend to agree with most of what you&#039;re saying but I think one issue you have missed, which is inherent in a waterfall model, is that designers and developers are not necessarily the same people with the same skills. Yes - a skilled builder could probably build his own house and design it on the fly, but I doubt the greatest works of architecture could have been constructed so. 

Of course, building the greatest works of architecture is not necessarily the aim in an IT context - but on the other hand, anything of sufficiently large scale needs shared vision and distribution of skills. I do wonder if design-by-code is the best way to achieve this?</description>
		<content:encoded><![CDATA[<p>I tend to agree with most of what you&#8217;re saying but I think one issue you have missed, which is inherent in a waterfall model, is that designers and developers are not necessarily the same people with the same skills. Yes &#8211; a skilled builder could probably build his own house and design it on the fly, but I doubt the greatest works of architecture could have been constructed so. </p>
<p>Of course, building the greatest works of architecture is not necessarily the aim in an IT context &#8211; but on the other hand, anything of sufficiently large scale needs shared vision and distribution of skills. I do wonder if design-by-code is the best way to achieve this?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.235 seconds -->

