<?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"
	>
<channel>
	<title>Comments on: What is good&#160;design?</title>
	<atom:link href="http://www.magpiebrain.com/blog/2005/09/15/what-is-good-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.magpiebrain.com/blog/2005/09/15/what-is-good-design/</link>
	<description>Sam Newman's blog</description>
	<pubDate>Fri, 08 Aug 2008 18:52:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Nick Drew</title>
		<link>http://www.magpiebrain.com/blog/2005/09/15/what-is-good-design/#comment-929</link>
		<dc:creator>Nick Drew</dc:creator>
		<pubDate>Thu, 22 Sep 2005 01:07:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2005/09/15/what-is-good-design/#comment-929</guid>
		<description>Yah - good design.  Hmmm - you remind me of my optician testing out lenses:  "Better or worse", he'd say, and try another lens.  "Better or worse".  The best lens was the one which ALLOWED ME TO SEE PROPERLY.  Was it a good design for a lens?  Maybe not for you.

A good design ( in a technical sense ) is a pretty simple concept.  Its the blueprint for something that emerges from a good design process.  

What's a good design process?  It's where you set up a set of constraints, and morph something until it satisfies those constraints.  You consider options, and evaluate each option against your constraints.  Where two designs are equivalent, you create a new constraint that allows you to choose between them.

I say "in a technical sense", because sometimes I use the term in as if it had some tangible manifestation: "Love the chair, great design".  I may mean its elegant, or stands out, or whatever.  But some of those chairs are just plain uncomfortable to sit on.





</description>
		<content:encoded><![CDATA[<p>Yah &#8211; good design.  Hmmm &#8211; you remind me of my optician testing out lenses:  &#8220;Better or worse&#8221;, he&#8217;d say, and try another lens.  &#8220;Better or worse&#8221;.  The best lens was the one which ALLOWED ME TO SEE PROPERLY.  Was it a good design for a lens?  Maybe not for you.</p>
<p>A good design ( in a technical sense ) is a pretty simple concept.  Its the blueprint for something that emerges from a good design process.  </p>
<p>What&#8217;s a good design process?  It&#8217;s where you set up a set of constraints, and morph something until it satisfies those constraints.  You consider options, and evaluate each option against your constraints.  Where two designs are equivalent, you create a new constraint that allows you to choose between them.</p>
<p>I say &#8220;in a technical sense&#8221;, because sometimes I use the term in as if it had some tangible manifestation: &#8220;Love the chair, great design&#8221;.  I may mean its elegant, or stands out, or whatever.  But some of those chairs are just plain uncomfortable to sit on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Newman</title>
		<link>http://www.magpiebrain.com/blog/2005/09/15/what-is-good-design/#comment-928</link>
		<dc:creator>Sam Newman</dc:creator>
		<pubDate>Thu, 15 Sep 2005 15:53:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2005/09/15/what-is-good-design/#comment-928</guid>
		<description>I think the _spirit_ of what Hani was trying to say is that the design accomodates unforseen requirements by being *flexible* - I simplified this by saying *easy to change* as the word flexible can mean many different things to many different people. I've often seen apparently highly configurable/highly flexible systems that were complex - perhaps getting a happy medium between flexibility and simplicity is key. 

If a design is easy to change it kind of follows that it's flexible (please note that by "change" I don't mean "configure" - too often highly configurable systems seem to be a result of abdication of responsibility on the part of the developer).</description>
		<content:encoded><![CDATA[<p>I think the <em>spirit</em> of what Hani was trying to say is that the design accomodates unforseen requirements by being <strong>flexible</strong> &#8211; I simplified this by saying <strong>easy to change</strong> as the word flexible can mean many different things to many different people. I&#8217;ve often seen apparently highly configurable/highly flexible systems that were complex &#8211; perhaps getting a happy medium between flexibility and simplicity is key. </p>
<p>If a design is easy to change it kind of follows that it&#8217;s flexible (please note that by &#8220;change&#8221; I don&#8217;t mean &#8220;configure&#8221; &#8211; too often highly configurable systems seem to be a result of abdication of responsibility on the part of the developer).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian McCallister</title>
		<link>http://www.magpiebrain.com/blog/2005/09/15/what-is-good-design/#comment-927</link>
		<dc:creator>Brian McCallister</dc:creator>
		<pubDate>Thu, 15 Sep 2005 15:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2005/09/15/what-is-good-design/#comment-927</guid>
		<description>I think he captured the correct gist of good design, though. A good design enables uses which were never envisioned or planned for. It is an "open" design which enables things, rather than allows the initial requirements to be fulfilled. Damned hard to capture in words =)</description>
		<content:encoded><![CDATA[<p>I think he captured the correct gist of good design, though. A good design enables uses which were never envisioned or planned for. It is an &#8220;open&#8221; design which enables things, rather than allows the initial requirements to be fulfilled. Damned hard to capture in words =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee</title>
		<link>http://www.magpiebrain.com/blog/2005/09/15/what-is-good-design/#comment-926</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Thu, 15 Sep 2005 14:03:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2005/09/15/what-is-good-design/#comment-926</guid>
		<description>__allows your code to do things you never expected it to have to do__

I'd say Hani is way off with this one, and agree with you. The only way a design can exceed expectations in this way is if it has been over engineered, and there is no guarantee that what has been implemented will work for the new usage, because it hasn't been designed with this usage in mind.</description>
		<content:encoded><![CDATA[<p><i>allows your code to do things you never expected it to have to do</i></p>
<p>I&#8217;d say Hani is way off with this one, and agree with you. The only way a design can exceed expectations in this way is if it has been over engineered, and there is no guarantee that what has been implemented will work for the new usage, because it hasn&#8217;t been designed with this usage in mind.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
