<?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: big red STOP signs</title>
	<atom:link href="http://silona.org/big-red-stop-signs/2009/06/25/feed/" rel="self" type="application/rss+xml" />
	<link>http://silona.org/big-red-stop-signs/2009/06/25/</link>
	<description>silona's central identity</description>
	<lastBuildDate>Wed, 14 Jul 2010 03:06:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Silona</title>
		<link>http://silona.org/big-red-stop-signs/2009/06/25/comment-page-1/#comment-44</link>
		<dc:creator>Silona</dc:creator>
		<pubDate>Wed, 01 Jul 2009 03:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://silona.org/?p=145#comment-44</guid>
		<description>I haven&#039;t read &quot;wisdom of crowds&quot; but seen his presentation too many times to be able to have the patience to read it.  I also remember having problems w it too but too tired to remember them right now.  Brain toasty from attending tooooo many thinktanks, conferences and summits right now!</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t read &#8220;wisdom of crowds&#8221; but seen his presentation too many times to be able to have the patience to read it.  I also remember having problems w it too but too tired to remember them right now.  Brain toasty from attending tooooo many thinktanks, conferences and summits right now!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miken12r</title>
		<link>http://silona.org/big-red-stop-signs/2009/06/25/comment-page-1/#comment-42</link>
		<dc:creator>miken12r</dc:creator>
		<pubDate>Wed, 01 Jul 2009 00:39:40 +0000</pubDate>
		<guid isPermaLink="false">http://silona.org/?p=145#comment-42</guid>
		<description>Community contributed? the problem is that oftentimes, the contributions are stolen property.  To me, this area doesn&#039;t need a new name, since it&#039;s existing for a very long time. It&#039;s called collaboration. 

By the way, have you read &quot;The Wisdom of Crowds&quot;?</description>
		<content:encoded><![CDATA[<p>Community contributed? the problem is that oftentimes, the contributions are stolen property.  To me, this area doesn&#8217;t need a new name, since it&#8217;s existing for a very long time. It&#8217;s called collaboration. </p>
<p>By the way, have you read &#8220;The Wisdom of Crowds&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Werdmuller</title>
		<link>http://silona.org/big-red-stop-signs/2009/06/25/comment-page-1/#comment-37</link>
		<dc:creator>Ben Werdmuller</dc:creator>
		<pubDate>Sat, 27 Jun 2009 22:09:49 +0000</pubDate>
		<guid isPermaLink="false">http://silona.org/?p=145#comment-37</guid>
		<description>Point taken on crowdsourced; the crowd isn&#039;t a machine, or a resource in the usual sense of the word (&quot;human resources&quot; always made me bristle). Will adjust my vocabulary.

(Community curated?)</description>
		<content:encoded><![CDATA[<p>Point taken on crowdsourced; the crowd isn&#8217;t a machine, or a resource in the usual sense of the word (&#8220;human resources&#8221; always made me bristle). Will adjust my vocabulary.</p>
<p>(Community curated?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miken12r</title>
		<link>http://silona.org/big-red-stop-signs/2009/06/25/comment-page-1/#comment-30</link>
		<dc:creator>miken12r</dc:creator>
		<pubDate>Thu, 25 Jun 2009 16:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://silona.org/?p=145#comment-30</guid>
		<description>Point taken about artificial complexity. The reason you had to do 27 level table join in the first place is because of limitations in the database system you had use. Relational databases are now so pervasive, they&#039;ve altered the way programmers think about data. Like looking at a cubist painting, data programmers view the world in a tabular format. 

But there are places where tabularism (RDBMS) breaks down--it&#039;s not perfectly descriptive. For one thing, it&#039;s not always possible to know the schema before you get the data.</description>
		<content:encoded><![CDATA[<p>Point taken about artificial complexity. The reason you had to do 27 level table join in the first place is because of limitations in the database system you had use. Relational databases are now so pervasive, they&#8217;ve altered the way programmers think about data. Like looking at a cubist painting, data programmers view the world in a tabular format. </p>
<p>But there are places where tabularism (RDBMS) breaks down&#8211;it&#8217;s not perfectly descriptive. For one thing, it&#8217;s not always possible to know the schema before you get the data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dbevarly</title>
		<link>http://silona.org/big-red-stop-signs/2009/06/25/comment-page-1/#comment-29</link>
		<dc:creator>dbevarly</dc:creator>
		<pubDate>Thu, 25 Jun 2009 14:32:30 +0000</pubDate>
		<guid isPermaLink="false">http://silona.org/?p=145#comment-29</guid>
		<description>Silona - Would tend to agree with you.  Viewing this vast landscape of social media solutions and solution providers one can appreciate the level of complexity that can create paralysis within an organization on direction or even adoption regardless of cost.  

I have found there are very simple solutions that can be enabled quickly with ease of use for non-techies (most of the users).  True there are limits in some cases to features/functions, design and flexibility.  

&quot;Different strokes for different folks,&quot; as they say.  Whether you&#039;re American Express or the local YMCA, an organization should begin by identifying its (potential) members&#039; needs then progress to their wants.  Keeping it simple, then, becomes more manageable and less complex.</description>
		<content:encoded><![CDATA[<p>Silona &#8211; Would tend to agree with you.  Viewing this vast landscape of social media solutions and solution providers one can appreciate the level of complexity that can create paralysis within an organization on direction or even adoption regardless of cost.  </p>
<p>I have found there are very simple solutions that can be enabled quickly with ease of use for non-techies (most of the users).  True there are limits in some cases to features/functions, design and flexibility.  </p>
<p>&#8220;Different strokes for different folks,&#8221; as they say.  Whether you&#8217;re American Express or the local YMCA, an organization should begin by identifying its (potential) members&#8217; needs then progress to their wants.  Keeping it simple, then, becomes more manageable and less complex.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
