<?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: The Need for Timely Software &#8211; SAP TechEd 2009</title>
	<atom:link href="http://www.redmonk.com/cote/2009/10/27/sapteched09/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/cote/2009/10/27/sapteched09/</link>
	<description>One foot in the muck, the other in utopia</description>
	<lastBuildDate>Thu, 24 May 2012 14:45:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Lotus â€“ IBM Software Analyst Connect 2009</title>
		<link>http://www.redmonk.com/cote/2009/10/27/sapteched09/comment-page-1/#comment-340907</link>
		<dc:creator>Lotus â€“ IBM Software Analyst Connect 2009</dc:creator>
		<pubDate>Thu, 19 Nov 2009 18:39:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2009/10/27/sapteched09/#comment-340907</guid>
		<description>[...] crew has their own problems â€“ see the enterprise rosary above â€“ and other elder companies like SAP have similar problems (and, even worse, bi-directional Stockholm syndrome), but tend to buy themselves the needed catch-up. From past performance, I have to be professionally [...]</description>
		<content:encoded><![CDATA[<p>[...] crew has their own problems â€“ see the enterprise rosary above â€“ and other elder companies like SAP have similar problems (and, even worse, bi-directional Stockholm syndrome), but tend to buy themselves the needed catch-up. From past performance, I have to be professionally [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: People Over Process &#187; Lotus &#8211; IBM Software Analyst Connect 2009</title>
		<link>http://www.redmonk.com/cote/2009/10/27/sapteched09/comment-page-1/#comment-340901</link>
		<dc:creator>People Over Process &#187; Lotus &#8211; IBM Software Analyst Connect 2009</dc:creator>
		<pubDate>Thu, 19 Nov 2009 17:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2009/10/27/sapteched09/#comment-340901</guid>
		<description>[...] their own problems &#8211; see the enterprise rosary above &#8211; and other elder companies like SAP have similar problems (and, even worse, bi-directional Stockholm syndrome), but tend to buy themselves the needed catch-up. From past performance, I have to be professionally [...]</description>
		<content:encoded><![CDATA[<p>[...] their own problems &#8211; see the enterprise rosary above &#8211; and other elder companies like SAP have similar problems (and, even worse, bi-directional Stockholm syndrome), but tend to buy themselves the needed catch-up. From past performance, I have to be professionally [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cote</title>
		<link>http://www.redmonk.com/cote/2009/10/27/sapteched09/comment-page-1/#comment-340710</link>
		<dc:creator>cote</dc:creator>
		<pubDate>Mon, 02 Nov 2009 22:49:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2009/10/27/sapteched09/#comment-340710</guid>
		<description>KK: yup, that&#039;s the perspective I hear from almost every SAP consultant, so it&#039;s nice to hear it again in a comment. And I think you&#039;re right in what you&#039;re outlining: it&#039;s not only SAP&#039;s job to nudge new technologies, but the enterprises themselves should figure out if being so risk averse with respect to new technologies is always the way to go.

Part of the issue is in the details there: for all the excellent stability and avoiding shutting down the Porsche factory (my favorite old SAP story I often hear), there doesn&#039;t seem to be  commonly used framework to figure out when change is worth the risk vs. staying the same. </description>
		<content:encoded><![CDATA[<p>KK: yup, that&#8217;s the perspective I hear from almost every SAP consultant, so it&#8217;s nice to hear it again in a comment. And I think you&#8217;re right in what you&#8217;re outlining: it&#8217;s not only SAP&#8217;s job to nudge new technologies, but the enterprises themselves should figure out if being so risk averse with respect to new technologies is always the way to go.</p>
<p>Part of the issue is in the details there: for all the excellent stability and avoiding shutting down the Porsche factory (my favorite old SAP story I often hear), there doesn&#8217;t seem to be  commonly used framework to figure out when change is worth the risk vs. staying the same. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KK Ramamoorthy</title>
		<link>http://www.redmonk.com/cote/2009/10/27/sapteched09/comment-page-1/#comment-340709</link>
		<dc:creator>KK Ramamoorthy</dc:creator>
		<pubDate>Mon, 02 Nov 2009 22:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2009/10/27/sapteched09/#comment-340709</guid>
		<description>Cote
Thanks for this nice article. A balanced perspective indeed. I see your point that SAP should be less risk averse when it comes to the latest and greatest in technology. However, the hard fact is that enterprise level software, changes at a far low pace than technology in general. For e.g., SAP came up with WebDynpro architecture (a move from traditional SAP GUI based Dynrpo framework) way back in 2005/2006 but at least in my customer base, it has only started pulling traction since last year. This is because customers generally want to stick to the proven frameworks when it comes to enterprise level software and don&#039;t want to be guinea pigs. As a consultant, even if I try to educate and offer the customer the latest and greatest, it is most often killed because of resource issues in post go-live support. An answer to that is developers/architects should educate themselves about the cutting edge technology more readily than what we see in majority of cases.
My 2 cents and as always, thanks for bringing your insights free of cost :-)</description>
		<content:encoded><![CDATA[<p>Cote<br />
Thanks for this nice article. A balanced perspective indeed. I see your point that SAP should be less risk averse when it comes to the latest and greatest in technology. However, the hard fact is that enterprise level software, changes at a far low pace than technology in general. For e.g., SAP came up with WebDynpro architecture (a move from traditional SAP GUI based Dynrpo framework) way back in 2005/2006 but at least in my customer base, it has only started pulling traction since last year. This is because customers generally want to stick to the proven frameworks when it comes to enterprise level software and don&#8217;t want to be guinea pigs. As a consultant, even if I try to educate and offer the customer the latest and greatest, it is most often killed because of resource issues in post go-live support. An answer to that is developers/architects should educate themselves about the cutting edge technology more readily than what we see in majority of cases.<br />
My 2 cents and as always, thanks for bringing your insights free of cost :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SAP TechEd 2009: Open Thinking</title>
		<link>http://www.redmonk.com/cote/2009/10/27/sapteched09/comment-page-1/#comment-340708</link>
		<dc:creator>SAP TechEd 2009: Open Thinking</dc:creator>
		<pubDate>Sun, 01 Nov 2009 17:14:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2009/10/27/sapteched09/#comment-340708</guid>
		<description>[...] that reflects the feel of a company in transition and a tad unsteady in its beliefs. Perhaps the best detailed wrap comes from Michael Cote, one of the Redmonk boys &#8211; it&#8217;s worth the reading and especially for detail around the [...]</description>
		<content:encoded><![CDATA[<p>[...] that reflects the feel of a company in transition and a tad unsteady in its beliefs. Perhaps the best detailed wrap comes from Michael Cote, one of the Redmonk boys &#8211; it&#8217;s worth the reading and especially for detail around the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cote</title>
		<link>http://www.redmonk.com/cote/2009/10/27/sapteched09/comment-page-1/#comment-340692</link>
		<dc:creator>cote</dc:creator>
		<pubDate>Fri, 30 Oct 2009 14:02:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2009/10/27/sapteched09/#comment-340692</guid>
		<description>Thanks for the internet of things cheering on there, sounds nice to me ;) </description>
		<content:encoded><![CDATA[<p>Thanks for the internet of things cheering on there, sounds nice to me ;) </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Bullotta</title>
		<link>http://www.redmonk.com/cote/2009/10/27/sapteched09/comment-page-1/#comment-340691</link>
		<dc:creator>Rick Bullotta</dc:creator>
		<pubDate>Fri, 30 Oct 2009 13:33:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2009/10/27/sapteched09/#comment-340691</guid>
		<description>The Luddite-ish perspective that the internet of things/web of things has no value for consumer products companies is equivalent to those who declared the Internet the next version of the CB radio... 
 
The old axiom &quot;the customer is always right&quot; is utter hogwash.  If you ask customers to define their problems and challenges, they subconsciously bound/limit their responses to what they perceive as possible.  Only 1% or so of customers are wired to think creatively as early adopters, and often they are the few who gain long-lasting competitive advantage as a result of discontinuities. 
 
Your &quot;rotting carrots&quot; example may not be the ideal one, but what about &quot;rotting milk&quot;?   The supply chain from cow to school cafeteria is incredibly short, and what CEO wants to wake up to a WSJ article about how his company impacted hundreds of 8 year olds? 
 
The applications go way, way beyond the traditional supply chain - despite the ignorant focus of even many researchers and practioners in the field on RFID as the &quot;internet of things&quot;.  It isn&#039;t.  Not even close. 
 
There will be some staggering, transformational, and permanent changes to how we think of applications and the way they interact with the &quot;real world&quot; in the next couple of years.  There are some interesting computer science problems to address to enable this, but there&#039;s plenty of work underway.  And the social implications will be significant as well. 
 
We&#039;re transitioning out of the industrial age into the information age (we most definitely are not there yet), and our schools and businesses are wired to educate us to think in &quot;industrial age&quot; ways -  a factory and assembly line mindset, even in regards to IT.  That&#039;ll change.  For a refresher, read or re-read Alvin Toffler&#039;s seminal work, &quot;The Third Wave&quot;, and see if it doesn&#039;t rewire a few synapses. 
 
Stay tuned.  And think big. </description>
		<content:encoded><![CDATA[<p>The Luddite-ish perspective that the internet of things/web of things has no value for consumer products companies is equivalent to those who declared the Internet the next version of the CB radio&#8230;</p>
<p>The old axiom &quot;the customer is always right&quot; is utter hogwash.  If you ask customers to define their problems and challenges, they subconsciously bound/limit their responses to what they perceive as possible.  Only 1% or so of customers are wired to think creatively as early adopters, and often they are the few who gain long-lasting competitive advantage as a result of discontinuities.</p>
<p>Your &quot;rotting carrots&quot; example may not be the ideal one, but what about &quot;rotting milk&quot;?   The supply chain from cow to school cafeteria is incredibly short, and what CEO wants to wake up to a WSJ article about how his company impacted hundreds of 8 year olds?</p>
<p>The applications go way, way beyond the traditional supply chain &#8211; despite the ignorant focus of even many researchers and practioners in the field on RFID as the &quot;internet of things&quot;.  It isn&#039;t.  Not even close.</p>
<p>There will be some staggering, transformational, and permanent changes to how we think of applications and the way they interact with the &quot;real world&quot; in the next couple of years.  There are some interesting computer science problems to address to enable this, but there&#039;s plenty of work underway.  And the social implications will be significant as well.</p>
<p>We&#039;re transitioning out of the industrial age into the information age (we most definitely are not there yet), and our schools and businesses are wired to educate us to think in &quot;industrial age&quot; ways &#8211;  a factory and assembly line mindset, even in regards to IT.  That&#039;ll change.  For a refresher, read or re-read Alvin Toffler&#039;s seminal work, &quot;The Third Wave&quot;, and see if it doesn&#039;t rewire a few synapses.</p>
<p>Stay tuned.  And think big. </p>
]]></content:encoded>
	</item>
</channel>
</rss>

