<?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 david ascher</title>
	<atom:link href="http://blog.ascher.ca/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ascher.ca</link>
	<description></description>
	<lastBuildDate>Sun, 19 May 2013 07:50:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on You are more than your job title by Aras</title>
		<link>http://blog.ascher.ca/2013/05/17/you-are-more-than-your-job-title/#comment-29561</link>
		<dc:creator>Aras</dc:creator>
		<pubDate>Sun, 19 May 2013 07:50:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ascher.ca/?p=807#comment-29561</guid>
		<description><![CDATA[David, I just want to thank you for writing this post, and for the slightly unconventional job posting. Honestly, when I saw the title, it immediately made sense to me. I am only wondering why more organizations dont ask for these qualification. Although I really like to be as good as possible at what I do -- I just cant code without thinking about the user experience or the interaction design. [Disclaimer: I did apply for this position] But really, I hope that I can find my own path and combine my interest for programming and interaction desigin regardless of whether I qualify for this position at this time. I know you are very busy man, but I would love to chat with you sometime and get some advice about how to survive as a fox.]]></description>
		<content:encoded><![CDATA[<p>David, I just want to thank you for writing this post, and for the slightly unconventional job posting. Honestly, when I saw the title, it immediately made sense to me. I am only wondering why more organizations dont ask for these qualification. Although I really like to be as good as possible at what I do &#8212; I just cant code without thinking about the user experience or the interaction design. [Disclaimer: I did apply for this position] But really, I hope that I can find my own path and combine my interest for programming and interaction desigin regardless of whether I qualify for this position at this time. I know you are very busy man, but I would love to chat with you sometime and get some advice about how to survive as a fox.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Personal computing in a decentralized world: a hopeful direction by Tim</title>
		<link>http://blog.ascher.ca/2013/03/07/decentralization/#comment-26048</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 20 Mar 2013 15:42:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ascher.ca/?p=784#comment-26048</guid>
		<description><![CDATA[David,  I enjoyed reading your article, though I&#039;m not sure how humane the future will be due to raspberry pi and the like.  You close with a question, &quot;What computing will she need, and who will build it?&quot;
I would like to suggest one answer that most of us forget or deny as a possibility, that being,  she doesn&#039;t need computing.
Yes, we can computerize relationships on a smaller, more personal scale using new tools, but why? Perhaps the benefit of not computerizing human relationships is a better proposal.  I do not mean to suggest that one may live as a Luddite, however as most interpersonal social media is used to communicate with people who are physically close to one another, it does strike me that the best of family, friends and co-workers could communicate in that luxurious and ancient manner of simply being with one another.
I know this is dreamy, but, as globalization kicks in to alter society there will be a need to produce artifacts that are non-digital, also the standard of living or at least the economies in developed countries will need to fall back in order to have development in other countries, this may produce a need or desire among people to forgo digital relationships and computerized work for a more self sustained economy - a cottage industry- that supports the human potential to build objects of meaning and value. I guess what I am saying is that we shouldn&#039;t expect that computerized technologies will be useful for everyone. Not everyone will program, or need to program, nor will the need for human relationships be fulfilled by technologies of communication.]]></description>
		<content:encoded><![CDATA[<p>David,  I enjoyed reading your article, though I&#8217;m not sure how humane the future will be due to raspberry pi and the like.  You close with a question, &#8220;What computing will she need, and who will build it?&#8221;<br />
I would like to suggest one answer that most of us forget or deny as a possibility, that being,  she doesn&#8217;t need computing.<br />
Yes, we can computerize relationships on a smaller, more personal scale using new tools, but why? Perhaps the benefit of not computerizing human relationships is a better proposal.  I do not mean to suggest that one may live as a Luddite, however as most interpersonal social media is used to communicate with people who are physically close to one another, it does strike me that the best of family, friends and co-workers could communicate in that luxurious and ancient manner of simply being with one another.<br />
I know this is dreamy, but, as globalization kicks in to alter society there will be a need to produce artifacts that are non-digital, also the standard of living or at least the economies in developed countries will need to fall back in order to have development in other countries, this may produce a need or desire among people to forgo digital relationships and computerized work for a more self sustained economy &#8211; a cottage industry- that supports the human potential to build objects of meaning and value. I guess what I am saying is that we shouldn&#8217;t expect that computerized technologies will be useful for everyone. Not everyone will program, or need to program, nor will the need for human relationships be fulfilled by technologies of communication.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simple analogies as taglines are dangerous: do better by Steve Fink</title>
		<link>http://blog.ascher.ca/2013/03/05/simple-analogies-as-taglines-are-dangerous-do-better/#comment-24353</link>
		<dc:creator>Steve Fink</dc:creator>
		<pubDate>Wed, 06 Mar 2013 21:24:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ascher.ca/?p=778#comment-24353</guid>
		<description><![CDATA[&quot;It&#039;s like YouTube, but started several years later, beginning with zero users, and in a niche that YouTube would invade if we proved it to be profitable.&quot;

Did I get it right that time?]]></description>
		<content:encoded><![CDATA[<p>&#8220;It&#8217;s like YouTube, but started several years later, beginning with zero users, and in a niche that YouTube would invade if we proved it to be profitable.&#8221;</p>
<p>Did I get it right that time?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simple analogies as taglines are dangerous: do better by Dave W</title>
		<link>http://blog.ascher.ca/2013/03/05/simple-analogies-as-taglines-are-dangerous-do-better/#comment-24348</link>
		<dc:creator>Dave W</dc:creator>
		<pubDate>Wed, 06 Mar 2013 20:21:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ascher.ca/?p=778#comment-24348</guid>
		<description><![CDATA[Totally agree, an analogy without a specific comparison is like a bar of soap.]]></description>
		<content:encoded><![CDATA[<p>Totally agree, an analogy without a specific comparison is like a bar of soap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simple analogies as taglines are dangerous: do better by david</title>
		<link>http://blog.ascher.ca/2013/03/05/simple-analogies-as-taglines-are-dangerous-do-better/#comment-24279</link>
		<dc:creator>david</dc:creator>
		<pubDate>Wed, 06 Mar 2013 05:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ascher.ca/?p=778#comment-24279</guid>
		<description><![CDATA[But my point is that the similarity you think you see there, may not be understood. Definitely agree that saying &quot;we&#039;re like X but unlike them, ____&quot; is a valuable rhetorical device.]]></description>
		<content:encoded><![CDATA[<p>But my point is that the similarity you think you see there, may not be understood. Definitely agree that saying &#8220;we&#8217;re like X but unlike them, ____&#8221; is a valuable rhetorical device.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simple analogies as taglines are dangerous: do better by Dan S</title>
		<link>http://blog.ascher.ca/2013/03/05/simple-analogies-as-taglines-are-dangerous-do-better/#comment-24278</link>
		<dc:creator>Dan S</dc:creator>
		<pubDate>Wed, 06 Mar 2013 04:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ascher.ca/?p=778#comment-24278</guid>
		<description><![CDATA[&quot;X is like Y&quot; can help to overcome some conceptual hurdles. 
The problem is that &quot;X is like Y&quot; is often taken as &quot;X is just a Y&quot; when what is important are the differences; what distinguishes X from Y.  Identity vs similarity.]]></description>
		<content:encoded><![CDATA[<p>&#8220;X is like Y&#8221; can help to overcome some conceptual hurdles.<br />
The problem is that &#8220;X is like Y&#8221; is often taken as &#8220;X is just a Y&#8221; when what is important are the differences; what distinguishes X from Y.  Identity vs similarity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ruminations on front end-centric webapps by Mark Surman</title>
		<link>http://blog.ascher.ca/2013/02/09/ruminations-on-front-end-centric-webapps/#comment-21608</link>
		<dc:creator>Mark Surman</dc:creator>
		<pubDate>Mon, 11 Feb 2013 17:20:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ascher.ca/?p=773#comment-21608</guid>
		<description><![CDATA[I agree w/ Boris and Chris: there is stuff in here even for people just starting with &#039;the basics&#039;. At least, there is if they want to get to making a &#039;real thing&#039; quickly. Ie. a thing that&#039;s &#039;sitey&#039; in that it doesn&#039;t just live in Facebook or YouTube. Also, architecturewise, I think there is alot to learn here from what we do w/ our Webmaker toolset in the realm of storage and publishing. I&#039;ve been saying we should look at Dropbox for storage for a while now.]]></description>
		<content:encoded><![CDATA[<p>I agree w/ Boris and Chris: there is stuff in here even for people just starting with &#8216;the basics&#8217;. At least, there is if they want to get to making a &#8216;real thing&#8217; quickly. Ie. a thing that&#8217;s &#8216;sitey&#8217; in that it doesn&#8217;t just live in Facebook or YouTube. Also, architecturewise, I think there is alot to learn here from what we do w/ our Webmaker toolset in the realm of storage and publishing. I&#8217;ve been saying we should look at Dropbox for storage for a while now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ruminations on front end-centric webapps by Dethe Elza</title>
		<link>http://blog.ascher.ca/2013/02/09/ruminations-on-front-end-centric-webapps/#comment-21427</link>
		<dc:creator>Dethe Elza</dc:creator>
		<pubDate>Sun, 10 Feb 2013 20:42:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ascher.ca/?p=773#comment-21427</guid>
		<description><![CDATA[Hi David,

The 404.html trick is great. The History API is great for storing state in various URLs, but I was wondering how a single-page static site would handle those different URLs as targets. Very cool hack.]]></description>
		<content:encoded><![CDATA[<p>Hi David,</p>
<p>The 404.html trick is great. The History API is great for storing state in various URLs, but I was wondering how a single-page static site would handle those different URLs as targets. Very cool hack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ruminations on front end-centric webapps by Brad Touesnard</title>
		<link>http://blog.ascher.ca/2013/02/09/ruminations-on-front-end-centric-webapps/#comment-21387</link>
		<dc:creator>Brad Touesnard</dc:creator>
		<pubDate>Sun, 10 Feb 2013 16:22:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ascher.ca/?p=773#comment-21387</guid>
		<description><![CDATA[This new mental model is very exciting. The tools are still a bit too immature for me though (I&#039;m no early adopter). The issue of single-page apps not being readable by search engines is probably the #1 sticking point. AirBnB and Twitter&#039;s frameworks seem to solve a lot of the issues, so that&#039;s very exciting.]]></description>
		<content:encoded><![CDATA[<p>This new mental model is very exciting. The tools are still a bit too immature for me though (I&#8217;m no early adopter). The issue of single-page apps not being readable by search engines is probably the #1 sticking point. AirBnB and Twitter&#8217;s frameworks seem to solve a lot of the issues, so that&#8217;s very exciting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ruminations on front end-centric webapps by Chris McAvoy</title>
		<link>http://blog.ascher.ca/2013/02/09/ruminations-on-front-end-centric-webapps/#comment-21245</link>
		<dc:creator>Chris McAvoy</dc:creator>
		<pubDate>Sun, 10 Feb 2013 02:05:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ascher.ca/?p=773#comment-21245</guid>
		<description><![CDATA[&quot;I’m not sure what this means for advanced webmaker skills. At the very least explaining some of the above to a broader audience is something we could do.&quot;

I think the ease of deployment, making publishing online as easy as saving to a filesystem, means webmaker skills become as important as basic word processing. None of the things you listed are WYSIWYG tools, they&#039;re all targeting skilled webmakers that don&#039;t necessarily have sysadmin chops. People sometimes question web literacy without server admin skills, but tools like these provide a lot of horsepower to people that invest in the core web making skillz.]]></description>
		<content:encoded><![CDATA[<p>&#8220;I’m not sure what this means for advanced webmaker skills. At the very least explaining some of the above to a broader audience is something we could do.&#8221;</p>
<p>I think the ease of deployment, making publishing online as easy as saving to a filesystem, means webmaker skills become as important as basic word processing. None of the things you listed are WYSIWYG tools, they&#8217;re all targeting skilled webmakers that don&#8217;t necessarily have sysadmin chops. People sometimes question web literacy without server admin skills, but tools like these provide a lot of horsepower to people that invest in the core web making skillz.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
