<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Thought Process : Process Thoughts &#187; Implementation</title>
	<atom:link href="http://www.joetennis.com/category/implementation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joetennis.com/blog</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sun, 18 Nov 2007 17:18:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Phone as Input device</title>
		<link>http://www.joetennis.com/blog/2007/10/29/phone-as-input-device/</link>
		<comments>http://www.joetennis.com/blog/2007/10/29/phone-as-input-device/#comments</comments>
		<pubDate>Mon, 29 Oct 2007 17:00:05 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Information Design]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[Strategy]]></category>

		<guid isPermaLink="false">http://www.joe10.com/2007/10/29/phone-as-input-device/</guid>
		<description><![CDATA[It never ceases to amaze me, that the best experience we seem to come up with for feeding a computer, after multi-touch this-and-that and semantic wonderment, and peer2peer, socially syndicated gobble-d-gook, are text fields, radio buttons, check boxes and menus. My Dad used to say that he had an unparalleled skill at creating errors on [...]]]></description>
			<content:encoded><![CDATA[<p>It never ceases to amaze me, that the best experience we seem to come up with for feeding a computer, after multi-touch this-and-that and semantic wonderment, and peer2peer, socially syndicated gobble-d-gook, are text fields, radio buttons, check boxes and menus.</p>
<p>My Dad used to say that he had an unparalleled skill at creating errors on &#8220;those Web forms&#8221; which he didn&#8217;t even realize were called forms.  <span id="more-101"></span></p>
<p>Cliff and I used to produce a bunch of securities trading applications for clients &#8211; first at Wells Fargo (an early, heck, maybe the first &#8220;Wells Trade site) then later a couple for WRH+Co. People were always tempted by &#8220;wireless solutions&#8221;, that is, transporting all those fields and buttons onto a screen the size of a match book. Cliff was fond of saying &#8220;our customers already have a wireless interface, and it works quite well; It&#8217;s called a Cel Phone and their human voice. When they want to make a trade, they call their broker and make a trade&#8221;.</p>
<p>Now, blogs, or micro-content distribution systems are getting into the voice game. Utterz let&#8217;s you call in a plog cast by phone&#8230; you dial the phone, you speak your mind, your voice shows up on their site &#8211; for now, without wanting to investigate their version of an interface, I&#8217;m going to assume these files can be accessed, syndicated and sliced and diced at will, like any well behaved pile of web content.</p>
<p>What could be really interesting out of this is to be able to post-facto reassemble a conversation, perhaps including multiple people. To be able to follow the train of thought that get&#8217;s spread out over time&#8230; perhaps months, and follow an articulate thread&#8230; from your iPod, from your networked audio player as you drive across country.</p>
<p>Return to English (or, insert your preferred native language here).</p>
<p>/Joe</p>
]]></content:encoded>
			<wfw:commentRss>http://www.joetennis.com/blog/2007/10/29/phone-as-input-device/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How project teams learn about agility</title>
		<link>http://www.joetennis.com/blog/2007/10/24/how-project-teams-learn-about-agility/</link>
		<comments>http://www.joetennis.com/blog/2007/10/24/how-project-teams-learn-about-agility/#comments</comments>
		<pubDate>Wed, 24 Oct 2007 16:00:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Culture]]></category>
		<category><![CDATA[WebDev]]></category>

		<guid isPermaLink="false">http://www.joe10.com/2007/10/24/how-project-teams-learn-about-agility/</guid>
		<description><![CDATA[Listening to conversations between designers and developers is an endless source of amusement. Contributors and visionaries from both camps will always have expectations and frame questions from the view of their own professional specialty. It gets even better, when a programmer and a designer discuss working Agile methodologies, and gets even better when they have [...]]]></description>
			<content:encoded><![CDATA[<p>Listening to conversations between designers and developers is an endless source of amusement. Contributors and visionaries from both camps will always have expectations and frame questions from the view of their own professional specialty.</p>
<p>It gets even better, when a programmer and a designer discuss working Agile methodologies, and gets even better when they have varying appreciations of what exactly agility is.<span id="more-88"></span></p>
<p>Designers love to have an open canvas to paint on. They hate to define requirements if it&#8217;s going to constrain their designs in any way. They seek agility so they can say &#8220;well, we&#8217;ll through some stuff up now, and refactor it later.&#8221;</p>
<p>Programmers of course see the aspects like &#8220;stories are agreements between business and production&#8221; ideal places to get formal definition of what they should spend their time on. They do need that&#8230; we all need that. Spending your time on low value things isn&#8217;t pleasant for anyone, and one of the big contributors to dissatisfaction.</p>
<p>Business folks tend to think of agility as the ability to add and change requirements whenever they want with little to no impact on dates, quality or resource commitment&#8230; the eternal &#8220;pick any two&#8221; triangle. Nothing&#8217;s changed.</p>
<p>Of course, there&#8217;s a balance to this. Those who have balanced agility with structure have done so after hard knocks in dealing with the different perspectives of business, design and business. One of the inevitable benefits of Agile Methods is getting these all too often separated groups talking together, sharing goals and speaking in English together earlier in the process, before it comes to blows at QA time!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.joetennis.com/blog/2007/10/24/how-project-teams-learn-about-agility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A new website is in order&#8230;</title>
		<link>http://www.joetennis.com/blog/2007/10/07/a-new-website/</link>
		<comments>http://www.joetennis.com/blog/2007/10/07/a-new-website/#comments</comments>
		<pubDate>Mon, 08 Oct 2007 05:11:41 +0000</pubDate>
		<dc:creator>joe10</dc:creator>
				<category><![CDATA[About Joe]]></category>
		<category><![CDATA[WebDev]]></category>

		<guid isPermaLink="false">http://www.joe10.com/2007/10/07/a-new-website/</guid>
		<description><![CDATA[So I decided that a new website is in order. Why? Well, the current most recent version of my site was made in 2003, and a lot&#8217;s changed since then. First off, I&#8217;m not in the business of providing custom solutions anymore: that site really showed the range of services I had been providing my [...]]]></description>
			<content:encoded><![CDATA[<p>So I decided that a new website is in order. Why? Well, the <strike>current</strike> most recent version of my site was made in 2003, and a lot&#8217;s changed since then.</p>
<p>First off, I&#8217;m not in the business of providing custom solutions anymore: that site really showed the range of services I had been providing my clients for over a decade and was intended to bring in new clients. As I&#8217;m currently employed I&#8217;m not really looking for clients, and my focus has narrowed from being a full service integrator to living up at the &#8220;Fuzzy Front End&#8221; of the development practice, where I start at the strategic planning point and pretty much back off once concepts have been approved.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.joetennis.com/blog/2007/10/07/a-new-website/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Semantic Web Introduction Roadmap</title>
		<link>http://www.joetennis.com/blog/2003/05/09/semantic-web-introduction-roadmap/</link>
		<comments>http://www.joetennis.com/blog/2003/05/09/semantic-web-introduction-roadmap/#comments</comments>
		<pubDate>Fri, 09 May 2003 16:48:52 +0000</pubDate>
		<dc:creator>joe10</dc:creator>
				<category><![CDATA[Interaction Design]]></category>
		<category><![CDATA[Meta Data]]></category>
		<category><![CDATA[Social Network Analysis]]></category>
		<category><![CDATA[WebDev]]></category>

		<guid isPermaLink="false">http://www.joe10.com/2003/05/09/semantic-web-introduction-roadmap/</guid>
		<description><![CDATA[Here is a list of links which explain, in increasing levels of sophistication, an initiative which is attempting to make sense of the glut of information on the web. The plan is to make it so computer programs can make logical assumptions and relationships between resources on the Web based on the semantics of their [...]]]></description>
			<content:encoded><![CDATA[<p>Here is a list of links which explain, in increasing levels of sophistication, an initiative which is attempting to make sense of the glut of information on the web.</p>
<p>The plan is to make it so computer programs can make logical assumptions and relationships between resources on the Web based on the semantics of their content. It is referred to as the Semantic Web.</p>
<p>The links that follow provide a gentle, if not brief, introduction to this initiative.</p>
<p><span id="more-78"></span><br />
EXECUTIVE GUIDE</p>
<p>First, there&#8217;s an audio interview with Tim Berners-Lee which isn&#8217;t strictly about the Semantic Web, but it&#8217;s an easy listen and gets some key concepts across:<br />
<a href="http://discover.npr.org/features/feature.jhtml?wfId=919751">Interview with Tim Berner-Lee</a></p>
<p>Next, Scientific American has a somewhat long but engaging piece explaining the Semantic Web in lay terms:<br />
<a href="http://www.sciam.com/article.cfm?articleID=00048144-10D2-1C70-84A9809EC588EF21">NPR: Scientific American: The Semantic Web</a></p>
<p>The incomparable Peter Moreville has a very readable account of his peering into the bubble of Social Network Analysis which has a set of &#8220;See Also&#8221; links which are enough to keep the average person busy into the next millennia.<br />
<a href="http://semanticstudios.com/publications/semantics/000006.php">Semantic Studios: Social Network Analysis</a></p>
<p>and Discover Mag Online has a lay persons look at software which makes similar inferences based on your Email inbox:<br />
<a href="http://discover.com/apr_03/feattech.html">Discover: Emerging Technology: Who Loves Ya, Baby?</a></p>
<p>On the software front, a company called Creo has a product called <a href="http://www2.creo.com/sixdegrees/">&#8220;Six Degrees&#8221;</a> which promises to semantically link files on your desktop in a meaningful way.</p>
<p>Finally, Big Blue has a couple article on using this stuff to unite and network your chain of friends &#8211; kind of &#8220;six degrees of separation&#8221; concept.</p>
<p><a href="http://www-106.ibm.com/developerworks/xml/library/x-foaf.html">IBM: XML Watch: Finding friends with XML and RDF</a></p>
<p>and</p>
<p><a href="http://www-106.ibm.com/developerworks/xml/library/x-foaf2.html">IBM: XML Watch: Support online communities with FOAF</a></p>
<p>There&#8217;s got to be something after that, but I&#8217;m not sure what. <a href="http://foafnaut.org/">FOAF-Naut</a> is about the graphically coolest thing I&#8217;ve seen. Requires the Adobe SVG plug-in though. Might be fun to improve in Flash.<br />
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</p>
<p>DEVELOPERS GUIDE</p>
<p>After that it leaves the ground rather abruptly, so if you want to dive in the deep end (if that&#8217;s not a train wreck of metaphors) then pop over to:</p>
<p>The WWW Consortium is the holder of the official Semantic Web torch:<br />
<a href="http://www.w3.org/2001/sw/">W3C: The Semantic Web</a></p>
<p><a href="http://rdfweb.org/">RDF Web</a><br />
is the home of lots of Friend of a Friend (FOAF) information</p>
<p><a href="http://www.disobey.com/detergent/2002/sw123/">This guy</a><br />
has many interesting links around this stuff</p>
]]></content:encoded>
			<wfw:commentRss>http://www.joetennis.com/blog/2003/05/09/semantic-web-introduction-roadmap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RDF Tutorial</title>
		<link>http://www.joetennis.com/blog/2003/04/08/73/</link>
		<comments>http://www.joetennis.com/blog/2003/04/08/73/#comments</comments>
		<pubDate>Tue, 08 Apr 2003 19:18:26 +0000</pubDate>
		<dc:creator>joe10</dc:creator>
				<category><![CDATA[Meta Data]]></category>
		<category><![CDATA[Social Network Analysis]]></category>

		<guid isPermaLink="false">http://www.joe10.com/2003/04/08/73/</guid>
		<description><![CDATA[Only in the SNA category because RDF seems an important vehicle for conecting related information. A good place to start for the begining technical explorer. RDF Tutorial &#8211; Part I: basic syntax and containers]]></description>
			<content:encoded><![CDATA[<p>Only in the SNA category because RDF seems an important vehicle for conecting related information. A good place to start for the begining technical explorer.</p>
<p><a href="http://www.zvon.org/xxl/RDFTutorial/General/book.html" title="RDF Tutorial - Part I: basic syntax and containers">RDF Tutorial &#8211; Part I: basic syntax and containers</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.joetennis.com/blog/2003/04/08/73/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

