<?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 for Platformability</title>
	<atom:link href="http://blog.caplin.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.caplin.com</link>
	<description>Single Dealer Platforms, Industry Expertise</description>
	<lastBuildDate>Thu, 02 Feb 2012 04:16:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on The Psychology of UX: Part 8 by MD</title>
		<link>http://blog.caplin.com/2011/11/30/the-psychology-of-ux-part-8/comment-page-1/#comment-6195</link>
		<dc:creator>MD</dc:creator>
		<pubDate>Thu, 02 Feb 2012 04:16:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.caplin.com/?p=7419#comment-6195</guid>
		<description>http://blog.caplin.com/2011/11/30/the-psychology-of-ux-part-8/
&quot;The emotional brain is (obviously) where all emotions are processed, and it is the root of impulses. Because of this it makes a big impact on our decision-making. The old brain and the emotional brain are very connected in the sense that if the old brain is highly aroused (by fear, or desire) the emotional brain deeply processes this information and etches it in our memory.&quot;

MD - Feb 1 2012 
The emotional brain is certainly highly sensitized to all sort of emotional input, but does this necessarily nullify human control of even the chiefist of impulses? Most Yanks (and Brits) exercise impulse control through established value systems, further directing impulse and desire. Yet this appears to be minimized in your analysis (excellent by the way). Yet I would argue that an established Value model, along with such amazing processing of environmental data, further separates human from non-human, and makes me and &quot;You&quot; special!

Finally, I wonder if your description of the dual coordination of old and emotional brains must always end in memory etching? Gate theory suggests a filtering process directing emotion, desire, and impulse toward or away from memory etching. Hence, input control.

Love your work!

From the Yank side,

MD
MD</description>
		<content:encoded><![CDATA[<p><a  href="http://blog.caplin.com/2011/11/30/the-psychology-of-ux-part-8/" rel="nofollow">http://blog.caplin.com/2011/11/30/the-psychology-of-ux-part-8/</a><br />
&#8220;The emotional brain is (obviously) where all emotions are processed, and it is the root of impulses. Because of this it makes a big impact on our decision-making. The old brain and the emotional brain are very connected in the sense that if the old brain is highly aroused (by fear, or desire) the emotional brain deeply processes this information and etches it in our memory.&#8221;</p>
<p>MD &#8211; Feb 1 2012<br />
The emotional brain is certainly highly sensitized to all sort of emotional input, but does this necessarily nullify human control of even the chiefist of impulses? Most Yanks (and Brits) exercise impulse control through established value systems, further directing impulse and desire. Yet this appears to be minimized in your analysis (excellent by the way). Yet I would argue that an established Value model, along with such amazing processing of environmental data, further separates human from non-human, and makes me and &#8220;You&#8221; special!</p>
<p>Finally, I wonder if your description of the dual coordination of old and emotional brains must always end in memory etching? Gate theory suggests a filtering process directing emotion, desire, and impulse toward or away from memory etching. Hence, input control.</p>
<p>Love your work!</p>
<p>From the Yank side,</p>
<p>MD<br />
MD</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The WHY of WAT by cmccormick</title>
		<link>http://blog.caplin.com/2012/01/27/the-why-of-wat/comment-page-1/#comment-6048</link>
		<dc:creator>cmccormick</dc:creator>
		<pubDate>Sun, 29 Jan 2012 15:21:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.caplin.com/?p=8184#comment-6048</guid>
		<description>That ate the link. Trying again: http://forums.thedailywtf.com/forums/t/25604.aspx</description>
		<content:encoded><![CDATA[<p>That ate the link. Trying again: <a  href="http://forums.thedailywtf.com/forums/t/25604.aspx" rel="nofollow">http://forums.thedailywtf.com/forums/t/25604.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The WHY of WAT by cmccormick</title>
		<link>http://blog.caplin.com/2012/01/27/the-why-of-wat/comment-page-1/#comment-6047</link>
		<dc:creator>cmccormick</dc:creator>
		<pubDate>Sun, 29 Jan 2012 15:20:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.caplin.com/?p=8184#comment-6047</guid>
		<description>A &lt;a href=&quot;http://forums.thedailywtf.com/forums/t/25604.aspx&quot; rel=&quot;nofollow&quot;&gt;related discussion&lt;/a&gt; of the presentation.

It being TDWTF, 90% of the comments were debating what &#039;wat&#039; means and how to pronounce it and the rest were about how the presentation wasn&#039;t funny and the audience sucked.</description>
		<content:encoded><![CDATA[<p>A <a  href="http://forums.thedailywtf.com/forums/t/25604.aspx" rel="nofollow">related discussion</a> of the presentation.</p>
<p>It being TDWTF, 90% of the comments were debating what &#8216;wat&#8217; means and how to pronounce it and the rest were about how the presentation wasn&#8217;t funny and the audience sucked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Finding the Ideal UX Wireframing Software by Daniel McQuillen</title>
		<link>http://blog.caplin.com/2010/12/16/finding-the-ideal-ux-wireframing-software/comment-page-1/#comment-6027</link>
		<dc:creator>Daniel McQuillen</dc:creator>
		<pubDate>Sun, 29 Jan 2012 03:03:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.caplin.com/?p=4614#comment-6027</guid>
		<description>Hi Vanessa,
Your readers might be interested in SimpleDiagrams as well. It can be helpful if you want a quick and simple way to sketch a use case or process. 
If you do give it a spin, would absolutely love to get your feedback (or from any of your readers) on how SD might better help common UX tasks.</description>
		<content:encoded><![CDATA[<p>Hi Vanessa,<br />
Your readers might be interested in SimpleDiagrams as well. It can be helpful if you want a quick and simple way to sketch a use case or process.<br />
If you do give it a spin, would absolutely love to get your feedback (or from any of your readers) on how SD might better help common UX tasks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The WHY of WAT by mark</title>
		<link>http://blog.caplin.com/2012/01/27/the-why-of-wat/comment-page-1/#comment-5993</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Sat, 28 Jan 2012 09:33:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.caplin.com/?p=8184#comment-5993</guid>
		<description>wat

I don&#039;t get it

Javascript confuses me.

As for Ruby, it is actually because of the parser.

When the parser sees

a = a

it believes that a was already created.

Or rather, it seems to not check about it at all. There is probably a reason why this was not changed, probably because it can&#039;t be easily changed.</description>
		<content:encoded><![CDATA[<p>wat</p>
<p>I don&#8217;t get it</p>
<p>Javascript confuses me.</p>
<p>As for Ruby, it is actually because of the parser.</p>
<p>When the parser sees</p>
<p>a = a</p>
<p>it believes that a was already created.</p>
<p>Or rather, it seems to not check about it at all. There is probably a reason why this was not changed, probably because it can&#8217;t be easily changed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The WHY of WAT by Adys</title>
		<link>http://blog.caplin.com/2012/01/27/the-why-of-wat/comment-page-1/#comment-5978</link>
		<dc:creator>Adys</dc:creator>
		<pubDate>Sat, 28 Jan 2012 04:42:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.caplin.com/?p=8184#comment-5978</guid>
		<description>It&#039;s funny to programmers who understand how types should and shouldn&#039;t interact with eachother.
In fact, it&#039;s pretty damn hilarious.

To those who have never seen anything more than phpbb&#039;s templates and javascript, here are some pointers from one that actually handles types much better:

&gt;&gt;&gt; [] + []
[]
&gt;&gt;&gt; {} + {}
TypeError: unsupported operand type(s) for +: &#039;dict&#039; and &#039;dict&#039;
&gt;&gt;&gt; {} + []
TypeError: unsupported operand type(s) for +: &#039;dict&#039; and &#039;list&#039;
&gt;&gt;&gt; [] + {}
TypeError: can only concatenate list (not &quot;dict&quot;) to list
&gt;&gt;&gt; &quot;wat&quot; - 1
TypeError: unsupported operand type(s) for -: &#039;str&#039; and &#039;int&#039;</description>
		<content:encoded><![CDATA[<p>It&#8217;s funny to programmers who understand how types should and shouldn&#8217;t interact with eachother.<br />
In fact, it&#8217;s pretty damn hilarious.</p>
<p>To those who have never seen anything more than phpbb&#8217;s templates and javascript, here are some pointers from one that actually handles types much better:</p>
<p>&gt;&gt;&gt; [] + []<br />
[]<br />
&gt;&gt;&gt; {} + {}<br />
TypeError: unsupported operand type(s) for +: &#8216;dict&#8217; and &#8216;dict&#8217;<br />
&gt;&gt;&gt; {} + []<br />
TypeError: unsupported operand type(s) for +: &#8216;dict&#8217; and &#8216;list&#8217;<br />
&gt;&gt;&gt; [] + {}<br />
TypeError: can only concatenate list (not &#8220;dict&#8221;) to list<br />
&gt;&gt;&gt; &#8220;wat&#8221; &#8211; 1<br />
TypeError: unsupported operand type(s) for -: &#8216;str&#8217; and &#8216;int&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How real-time does real-time have to be? by Jonathan</title>
		<link>http://blog.caplin.com/2009/12/09/how-real-time-does-real-time-have-to-be/comment-page-1/#comment-5971</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Fri, 27 Jan 2012 17:51:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.caplin.com/?p=737#comment-5971</guid>
		<description>Realtime is well and good, but if you change things faster than humans can read them, bad things happen. 

I&#039;m already fed up of google displaying some results that catch my eye whilst I&#039;m typing, but which have vanished by the time I stop pressing keys.</description>
		<content:encoded><![CDATA[<p>Realtime is well and good, but if you change things faster than humans can read them, bad things happen. </p>
<p>I&#8217;m already fed up of google displaying some results that catch my eye whilst I&#8217;m typing, but which have vanished by the time I stop pressing keys.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The WHY of WAT by Zach</title>
		<link>http://blog.caplin.com/2012/01/27/the-why-of-wat/comment-page-1/#comment-5970</link>
		<dc:creator>Zach</dc:creator>
		<pubDate>Fri, 27 Jan 2012 17:51:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.caplin.com/?p=8184#comment-5970</guid>
		<description>Even knowing all this, the video was still pretty funny because it pokes fun at the limitations of the primitive operators. The fact that I know where those limitations are doesn&#039;t make it less funny that {} + {} = NaN because it&#039;s like watching a fish try to climb a tree (i.e., pretty damn funny).</description>
		<content:encoded><![CDATA[<p>Even knowing all this, the video was still pretty funny because it pokes fun at the limitations of the primitive operators. The fact that I know where those limitations are doesn&#8217;t make it less funny that {} + {} = NaN because it&#8217;s like watching a fish try to climb a tree (i.e., pretty damn funny).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

