<?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: Subtlety hinders grokability</title>
	<atom:link href="http://brianwill.net/blog/2008/03/17/subtlety-hinders-grokability/feed/" rel="self" type="application/rss+xml" />
	<link>http://brianwill.net/blog/2008/03/17/subtlety-hinders-grokability/</link>
	<description></description>
	<lastBuildDate>Thu, 25 Mar 2010 06:32:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nicholas Harris</title>
		<link>http://brianwill.net/blog/2008/03/17/subtlety-hinders-grokability/comment-page-1/#comment-4052</link>
		<dc:creator>Nicholas Harris</dc:creator>
		<pubDate>Tue, 06 Oct 2009 15:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/2008/03/17/subtlety-hinders-grokability/#comment-4052</guid>
		<description>I agree. Yet it isn&#039;t just euphoria that &#039;blinds the designer to some side-effect&#039;, but a practically unavoidable &quot;tunnel-vision&quot; that prevents the designer from being mindful of all aspects and interdependencies of their language&#039;s syntax and semantics. There is just too much to be familiar with whilst the design is in flux. The pragmatic designer concentrates on one particular area, but it is all too easy to forget about a superficially unrelated aspect, especially if that part of the design has not been looked at recently. I have found this to be a great problem in fusing the styles and rich capabilities of my multi-paradigm language. A simpler, one paradigm language would present far fewer difficulties.</description>
		<content:encoded><![CDATA[<p>I agree. Yet it isn&#8217;t just euphoria that &#8216;blinds the designer to some side-effect&#8217;, but a practically unavoidable &#8220;tunnel-vision&#8221; that prevents the designer from being mindful of all aspects and interdependencies of their language&#8217;s syntax and semantics. There is just too much to be familiar with whilst the design is in flux. The pragmatic designer concentrates on one particular area, but it is all too easy to forget about a superficially unrelated aspect, especially if that part of the design has not been looked at recently. I have found this to be a great problem in fusing the styles and rich capabilities of my multi-paradigm language. A simpler, one paradigm language would present far fewer difficulties.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
