<?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 for observing DESIGN</title>
	<atom:link href="http://www.observingdesign.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.observingdesign.com</link>
	<description>impact of design on everyday life</description>
	<pubDate>Wed, 10 Mar 2010 11:38:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>Comment on ESCALATORS: Why are they so BORING? by Carleton</title>
		<link>http://www.observingdesign.com/2008/11/escalators-why-are-they-so-boring/#comment-8</link>
		<dc:creator>Carleton</dc:creator>
		<pubDate>Fri, 21 Nov 2008 19:13:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.observingdesign.com/?p=26#comment-8</guid>
		<description>I would be very curious to see a curved escalator in person.  It is much more difficult to design and build a curved escalator over a straight one.  I would have thought it was impossible with out your photographic proof.</description>
		<content:encoded><![CDATA[<p>I would be very curious to see a curved escalator in person.  It is much more difficult to design and build a curved escalator over a straight one.  I would have thought it was impossible with out your photographic proof.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ESCALATORS: Why are they so BORING? by Andrea</title>
		<link>http://www.observingdesign.com/2008/11/escalators-why-are-they-so-boring/#comment-7</link>
		<dc:creator>Andrea</dc:creator>
		<pubDate>Fri, 21 Nov 2008 17:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.observingdesign.com/?p=26#comment-7</guid>
		<description>Escalator or not?
This is a picture of a moving ramp I encountered in Copenhagen, at first glance I thought it was an escalator.  Although the looks are pretty standard the experience of getting on and off was engaging as it was new and not as easy as stepping onto an escalator.  

http://picasaweb.google.com/andrea.beukema/Copenhagen#5270050356740362562</description>
		<content:encoded><![CDATA[<p>Escalator or not?<br />
This is a picture of a moving ramp I encountered in Copenhagen, at first glance I thought it was an escalator.  Although the looks are pretty standard the experience of getting on and off was engaging as it was new and not as easy as stepping onto an escalator.  </p>
<p><a href="http://picasaweb.google.com/andrea.beukema/Copenhagen#5270050356740362562" rel="nofollow">http://picasaweb.google.com/andrea.beukema/Copenhagen#5270050356740362562</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wrong information or no information? by Michael Spitzer</title>
		<link>http://www.observingdesign.com/2008/11/wrong-information-or-no-information/#comment-6</link>
		<dc:creator>Michael Spitzer</dc:creator>
		<pubDate>Fri, 21 Nov 2008 03:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://observingdesign.wordpress.com/?p=25#comment-6</guid>
		<description>Thanks for the comment Carleton.  I would agree that they don't turn it off because someone spent a lot of money on it and turning it off would admit failure.  If it works around 50% of the time (although it is probably less than that), it seems that that is good enough for some.  

Just tonight I was told by the computer voice that there was a train arriving, followed by it telling me that a train would arrive in 3 minutes, followed by a train arriving, at which point (after it stopped) was I told again that the train was now arriving.  

I am sure there are major design challenges also, like you said, but every other city I have been to with a system like this seems to get it right at least enough for people to trust the system (DC, San Francisco, London, Paris).  Yes, the NYC system is old, but so is Paris'.  It is also very large -- but so far we're just dealing with the L line which is about the simplest line in the system (just back and forth, no express tracks, etc.).  If you think about it, how hard could it really be?  I could stand it if it breaks down entirely now and again, but the fact that is is just plain wrong just doesn't make sense.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Carleton.  I would agree that they don&#8217;t turn it off because someone spent a lot of money on it and turning it off would admit failure.  If it works around 50% of the time (although it is probably less than that), it seems that that is good enough for some.  </p>
<p>Just tonight I was told by the computer voice that there was a train arriving, followed by it telling me that a train would arrive in 3 minutes, followed by a train arriving, at which point (after it stopped) was I told again that the train was now arriving.  </p>
<p>I am sure there are major design challenges also, like you said, but every other city I have been to with a system like this seems to get it right at least enough for people to trust the system (DC, San Francisco, London, Paris).  Yes, the NYC system is old, but so is Paris&#8217;.  It is also very large &#8212; but so far we&#8217;re just dealing with the L line which is about the simplest line in the system (just back and forth, no express tracks, etc.).  If you think about it, how hard could it really be?  I could stand it if it breaks down entirely now and again, but the fact that is is just plain wrong just doesn&#8217;t make sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wrong information or no information? by Carleton</title>
		<link>http://www.observingdesign.com/2008/11/wrong-information-or-no-information/#comment-5</link>
		<dc:creator>Carleton</dc:creator>
		<pubDate>Thu, 20 Nov 2008 04:15:21 +0000</pubDate>
		<guid isPermaLink="false">http://observingdesign.wordpress.com/?p=25#comment-5</guid>
		<description>I have to say, I have been curious about this for a long time.  In particular, how was this system intended to work?  And why does it fail so miserably?  I can't imagine proposing a system for tracking the trains which could be so unpredictable, but then again... I don't know what the design challenges are.

I am also confused as to why they have not turned it off or improved it's performance.  I would assume it's to save face.</description>
		<content:encoded><![CDATA[<p>I have to say, I have been curious about this for a long time.  In particular, how was this system intended to work?  And why does it fail so miserably?  I can&#8217;t imagine proposing a system for tracking the trains which could be so unpredictable, but then again&#8230; I don&#8217;t know what the design challenges are.</p>
<p>I am also confused as to why they have not turned it off or improved it&#8217;s performance.  I would assume it&#8217;s to save face.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Thinking about context by Rebecca</title>
		<link>http://www.observingdesign.com/2008/11/thinking-about-context/#comment-4</link>
		<dc:creator>Rebecca</dc:creator>
		<pubDate>Tue, 11 Nov 2008 01:32:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.observingdesign.com/?p=22#comment-4</guid>
		<description>That's a really interesting and disturbing image. It raises a question... Even if I had thought about the context of design a priori, I still might not have pictured all the weird contexts my design could have landed in. How then do you think about context without going crazy and trying to think of ALL the contexts. Is there a general question that is still more specific than, "What will the context be?" to help designers think through a potentially embarrassing display?</description>
		<content:encoded><![CDATA[<p>That&#8217;s a really interesting and disturbing image. It raises a question&#8230; Even if I had thought about the context of design a priori, I still might not have pictured all the weird contexts my design could have landed in. How then do you think about context without going crazy and trying to think of ALL the contexts. Is there a general question that is still more specific than, &#8220;What will the context be?&#8221; to help designers think through a potentially embarrassing display?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Etch-a-sketch and the iPhone by Carleton</title>
		<link>http://www.observingdesign.com/2008/11/etch-a-sketch-and-the-iphone/#comment-3</link>
		<dc:creator>Carleton</dc:creator>
		<pubDate>Sat, 08 Nov 2008 20:05:55 +0000</pubDate>
		<guid isPermaLink="false">http://observingdesign.wordpress.com/?p=29#comment-3</guid>
		<description>I would argue that a minimum of 4 fingers are required to erch-a-sketch.  Those knobs are really hard to turn with out pinching them!</description>
		<content:encoded><![CDATA[<p>I would argue that a minimum of 4 fingers are required to erch-a-sketch.  Those knobs are really hard to turn with out pinching them!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cell phone key lock (almost) by Joslyn</title>
		<link>http://www.observingdesign.com/2008/11/cell-phone-key-lock-almost/#comment-2</link>
		<dc:creator>Joslyn</dc:creator>
		<pubDate>Fri, 07 Nov 2008 20:03:54 +0000</pubDate>
		<guid isPermaLink="false">http://observingdesign.wordpress.com/?p=17#comment-2</guid>
		<description>Ok, I just tried this on my BlackBerry Curve. I was able to turn the phone off when the keyboard was locked, but when I turned it back on, the keyboard remained locked.
Interesting, though!</description>
		<content:encoded><![CDATA[<p>Ok, I just tried this on my BlackBerry Curve. I was able to turn the phone off when the keyboard was locked, but when I turned it back on, the keyboard remained locked.<br />
Interesting, though!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
