<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Law 6: Context</title>
	<link>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/</link>
	<description>simplicity resources for design, business, technology, and life</description>
	<pubDate>Tue, 07 Oct 2008 21:38:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Sharad Sharma</title>
		<link>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-8296</link>
		<pubDate>Sun, 20 Apr 2008 08:57:56 +0000</pubDate>
		<guid>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-8296</guid>
					<description>Let's differentiate between beneath and surronding.
What i interpret is that the surface or problem you are trying to simplify depends a lot on the surronding. We need deep understanding of the surrounding to 
1. Help us know the current limitations imposed by surrondings. 
2. We can be influenced by surrounding.
3. We can make use of any breakthrough in surronding to achieve next level of simplicity.</description>
		<content:encoded><![CDATA[<p>Let&#8217;s differentiate between beneath and surronding.<br />
What i interpret is that the surface or problem you are trying to simplify depends a lot on the surronding. We need deep understanding of the surrounding to<br />
1. Help us know the current limitations imposed by surrondings.<br />
2. We can be influenced by surrounding.<br />
3. We can make use of any breakthrough in surronding to achieve next level of simplicity.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: christine</title>
		<link>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-8161</link>
		<pubDate>Thu, 24 Jan 2008 15:46:05 +0000</pubDate>
		<guid>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-8161</guid>
					<description>thanks</description>
		<content:encoded><![CDATA[<p>thanks
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: maeda</title>
		<link>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-8059</link>
		<pubDate>Fri, 28 Dec 2007 15:27:14 +0000</pubDate>
		<guid>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-8059</guid>
					<description>Nice. Thanks, John</description>
		<content:encoded><![CDATA[<p>Nice. Thanks, John
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: plc</title>
		<link>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-8058</link>
		<pubDate>Fri, 28 Dec 2007 15:23:26 +0000</pubDate>
		<guid>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-8058</guid>
					<description>context - what holds story together... embrace = engaged</description>
		<content:encoded><![CDATA[<p>context - what holds story together&#8230; embrace = engaged
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bernardo</title>
		<link>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-7762</link>
		<pubDate>Wed, 24 Oct 2007 16:49:00 +0000</pubDate>
		<guid>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-7762</guid>
					<description>Dr Gross. I think you're overanalizing this. 

I think that the point is that simplicity can be achieved by creating a context to embrace it. 

Apple's remote is extremely simple: five buton navigation, plus one button that works both as a startup and as an exit button. In it's periphery we have Front Row, which allows the remote to be simple by giving a simple interface (or context) in which to exist. Take that remote and give it a Windows interface and it's no longer simple because it's surrounded by a context that doesn't complement it (it would probably have too many menu options that would be hard to navigate with a five button remote, and then you would have to go through multiple screens and levels, hence you'd need a more elaborate and complex remote).

You're talking about &quot;divide and conquer&quot; (very commonly used in programming, which could explain your code example), or maybe even about hiding reality.</description>
		<content:encoded><![CDATA[<p>Dr Gross. I think you&#8217;re overanalizing this. </p>
<p>I think that the point is that simplicity can be achieved by creating a context to embrace it. </p>
<p>Apple&#8217;s remote is extremely simple: five buton navigation, plus one button that works both as a startup and as an exit button. In it&#8217;s periphery we have Front Row, which allows the remote to be simple by giving a simple interface (or context) in which to exist. Take that remote and give it a Windows interface and it&#8217;s no longer simple because it&#8217;s surrounded by a context that doesn&#8217;t complement it (it would probably have too many menu options that would be hard to navigate with a five button remote, and then you would have to go through multiple screens and levels, hence you&#8217;d need a more elaborate and complex remote).</p>
<p>You&#8217;re talking about &#8220;divide and conquer&#8221; (very commonly used in programming, which could explain your code example), or maybe even about hiding reality.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dr Gross</title>
		<link>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-1833</link>
		<pubDate>Mon, 02 Apr 2007 04:51:13 +0000</pubDate>
		<guid>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-1833</guid>
					<description>Hey Johan

I have concluded the meaning of this law as follows.

What looks simple (appearing in the periperhy of simplicity) is defintly not simple because there is alot more to it then what meets the eye(peripheral).

Examples could be any show of talent, wrestling, yo yo'ng, or a website that looks very clean and simple, break down the code and it may not be the case.</description>
		<content:encoded><![CDATA[<p>Hey Johan</p>
<p>I have concluded the meaning of this law as follows.</p>
<p>What looks simple (appearing in the periperhy of simplicity) is defintly not simple because there is alot more to it then what meets the eye(peripheral).</p>
<p>Examples could be any show of talent, wrestling, yo yo&#8217;ng, or a website that looks very clean and simple, break down the code and it may not be the case.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Johan</title>
		<link>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-1694</link>
		<pubDate>Sat, 31 Mar 2007 13:00:40 +0000</pubDate>
		<guid>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-1694</guid>
					<description>Dr Gross&amp;#62; I don't think the simplicity of what is at the peripheral is what this rule is concerned about. 

If something is &quot;close&quot; to the core, then &quot;it must have something to do with it&quot;, hence, what surrounds simplicity must be *important*. This is my interpretation. :)</description>
		<content:encoded><![CDATA[<p>Dr Gross&gt; I don&#8217;t think the simplicity of what is at the peripheral is what this rule is concerned about. </p>
<p>If something is &#8220;close&#8221; to the core, then &#8220;it must have something to do with it&#8221;, hence, what surrounds simplicity must be *important*. This is my interpretation. <img src='http://lawsofsimplicity.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dr Gross</title>
		<link>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-672</link>
		<pubDate>Thu, 08 Feb 2007 01:48:41 +0000</pubDate>
		<guid>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-672</guid>
					<description>It makes sense when I think deep, but when I try to explain it seems it should be 

What lies in the periphery of simplicity is deﬁnitely not Simple (peripheral).</description>
		<content:encoded><![CDATA[<p>It makes sense when I think deep, but when I try to explain it seems it should be </p>
<p>What lies in the periphery of simplicity is deﬁnitely not Simple (peripheral).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dr Gross</title>
		<link>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-604</link>
		<pubDate>Sat, 20 Jan 2007 08:32:03 +0000</pubDate>
		<guid>http://lawsofsimplicity.com/2006/07/23/law-6-context-2/#comment-604</guid>
					<description>Things are not always what they seem.</description>
		<content:encoded><![CDATA[<p>Things are not always what they seem.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
