



















































<?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: AJAX book, Web 2.0 Workgroup and T-dot Enablr</title>
	<atom:link href="http://davidcrow.ca/article/724/ajax-book-web-20-workgroup-and-t-dot-enablr/feed" rel="self" type="application/rss+xml" />
	<link>http://davidcrow.ca/article/724/ajax-book-web-20-workgroup-and-t-dot-enablr</link>
	<description>Helping companies with marketing, product strategy, user experience design, and technology development.</description>
	<lastBuildDate>Thu, 22 Jul 2010 15:01:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Ken King &#124; King Marketing</title>
		<link>http://davidcrow.ca/article/724/ajax-book-web-20-workgroup-and-t-dot-enablr/comment-page-1#comment-175</link>
		<dc:creator>Ken King &#124; King Marketing</dc:creator>
		<pubDate>Wed, 12 Oct 2005 22:18:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davidcrow.ca/?p=250#comment-175</guid>
		<description>&lt;p&gt;David,&lt;/p&gt;
&lt;p&gt;
Thanks for the kind words. &lt;/p&gt;
&lt;p&gt;
Enablr is indeed a front-end for wetware, at least to start. Down the road we will add an automated speech-to-text option for transcribr, among other technological improvements to the services.&lt;/p&gt;
&lt;p&gt;
Our decision to go this route was motivated by two things Ã¢â‚¬&#039; making it simple for the user to get what they want, and doing something &lt;strong&gt;now.&lt;/strong&gt; The frontend experience came first, wetware was what we could do right away, and next weÃ¢â‚¬â„¢ll move on to refining the backend.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>
Thanks for the kind words. </p>
<p>
Enablr is indeed a front-end for wetware, at least to start. Down the road we will add an automated speech-to-text option for transcribr, among other technological improvements to the services.</p>
<p>
Our decision to go this route was motivated by two things Ã¢â‚¬&#39; making it simple for the user to get what they want, and doing something <strong>now.</strong> The frontend experience came first, wetware was what we could do right away, and next weÃ¢â‚¬â„¢ll move on to refining the backend.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
