<?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 Miko Matsumura Platform Software Executive Technologist</title>
	<atom:link href="http://www.miko.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.miko.com</link>
	<description>Software Technology Futures</description>
	<lastBuildDate>Fri, 18 Mar 2011 10:45:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on HP&#8217;s Strategy Tagcloud Buzzword Bingo Vortex of Doom by Does That API Go With This Outfit?</title>
		<link>http://www.miko.com/2011/03/14/hps-strategy-tagcloud-buzzword-bingo-vortex-of-doom/#comment-100</link>
		<dc:creator>Does That API Go With This Outfit?</dc:creator>
		<pubDate>Fri, 18 Mar 2011 10:45:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.miko.com/?p=176#comment-100</guid>
		<description>[...] how they communicate. It&#8217;s not about the smooth talker with the sharp suit. It&#8217;s not about the buzzwords. It&#8217;s about authenticity and the shared [...]</description>
		<content:encoded><![CDATA[<p>[...] how they communicate. It&#8217;s not about the smooth talker with the sharp suit. It&#8217;s not about the buzzwords. It&#8217;s about authenticity and the shared [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About Miko by Five definitions toward the maturing of Enterprise 2.0</title>
		<link>http://www.miko.com/about/#comment-71</link>
		<dc:creator>Five definitions toward the maturing of Enterprise 2.0</dc:creator>
		<pubDate>Tue, 03 Nov 2009 04:03:12 +0000</pubDate>
		<guid isPermaLink="false">#comment-71</guid>
		<description>[...] this guest blog post, Miko Matsumura, Vice President and Chief Strategist of Software AG, offers a humorous look at the Enterprise 2.0 [...]</description>
		<content:encoded><![CDATA[<p>[...] this guest blog post, Miko Matsumura, Vice President and Chief Strategist of Software AG, offers a humorous look at the Enterprise 2.0 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About Miko by IT Project Failures mobile edition</title>
		<link>http://www.miko.com/about/#comment-70</link>
		<dc:creator>IT Project Failures mobile edition</dc:creator>
		<pubDate>Tue, 03 Nov 2009 03:08:22 +0000</pubDate>
		<guid isPermaLink="false">#comment-70</guid>
		<description>[...] a perfect time to re-examine the &quot;enterprise&quot; part of Enterprise 2.0. In this guest blog post, Miko Matsumura, Vice President and Chief Strategist of Software AG, offers a humorous look at the Enterprise 2.0 [...]</description>
		<content:encoded><![CDATA[<p>[...] a perfect time to re-examine the &#8220;enterprise&#8221; part of Enterprise 2.0. In this guest blog post, Miko Matsumura, Vice President and Chief Strategist of Software AG, offers a humorous look at the Enterprise 2.0 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Entropic heat death of IT by nic.harvard</title>
		<link>http://www.miko.com/2009/07/07/entropic-heat-death-of-it/#comment-67</link>
		<dc:creator>nic.harvard</dc:creator>
		<pubDate>Tue, 11 Aug 2009 22:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.soacenter.com/?p=189#comment-67</guid>
		<description>Excellent observations:

A few years ago, one of my peers noted, &quot; a few more projects like that and i am done!&quot;
She had done an excellent job, but post-implementation, around 20% of her time thereafter was taken up with support and troubleshooting.

There are two main differences between entropic or anti-entropic system or solution programmes:
1) Entropic ones are all short-sighted point solutions
1.1) Anti-entropic ones address the longer term, and look at medium-long term TCO, and address the support/sustain/maintain issues from day 1. Often these can be more costly than licence and implementation even (have i started to speak about shelfware and deployment and adoption yet?)
2.) Entropic &quot;solutions&quot; don&#039;t see their place in the greater scheme of things. 
Biologically, they are at worst cancers, or at best, localised pathologies that will dies soon and not harm the greater organism in a significant way.
2.1) Anti-entropic systems range from (at worst) parasitic, but benign, through to symbiotic, mutualist, or commensualist situations.
This is a sign of either a good, or a lucky architecture.</description>
		<content:encoded><![CDATA[<p>Excellent observations:</p>
<p>A few years ago, one of my peers noted, &#8221; a few more projects like that and i am done!&#8221;<br />
She had done an excellent job, but post-implementation, around 20% of her time thereafter was taken up with support and troubleshooting.</p>
<p>There are two main differences between entropic or anti-entropic system or solution programmes:<br />
1) Entropic ones are all short-sighted point solutions<br />
1.1) Anti-entropic ones address the longer term, and look at medium-long term TCO, and address the support/sustain/maintain issues from day 1. Often these can be more costly than licence and implementation even (have i started to speak about shelfware and deployment and adoption yet?)<br />
2.) Entropic &#8220;solutions&#8221; don&#8217;t see their place in the greater scheme of things.<br />
Biologically, they are at worst cancers, or at best, localised pathologies that will dies soon and not harm the greater organism in a significant way.<br />
2.1) Anti-entropic systems range from (at worst) parasitic, but benign, through to symbiotic, mutualist, or commensualist situations.<br />
This is a sign of either a good, or a lucky architecture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SOA Arrogance is Dead by nic.harvard</title>
		<link>http://www.miko.com/2009/08/07/soa-arrogance-is-dead/#comment-66</link>
		<dc:creator>nic.harvard</dc:creator>
		<pubDate>Tue, 11 Aug 2009 21:16:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.soacenter.com/?p=191#comment-66</guid>
		<description>I agree with and endorse this entire article, except for one part:
&quot;Architects are smart people&quot;
I am one, and all i know is how *little* i know, and how many questions i need to ask every day.

If all the guys who sat in my chair before me, and kept this seat warm were so smart, howcome i have a job?</description>
		<content:encoded><![CDATA[<p>I agree with and endorse this entire article, except for one part:<br />
&#8220;Architects are smart people&#8221;<br />
I am one, and all i know is how *little* i know, and how many questions i need to ask every day.</p>
<p>If all the guys who sat in my chair before me, and kept this seat warm were so smart, howcome i have a job?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting fit for SOA with Governance Tools by kamen</title>
		<link>http://www.miko.com/2008/10/23/getting-fit-for-soa-with-governance-tools/#comment-10</link>
		<dc:creator>kamen</dc:creator>
		<pubDate>Tue, 04 Nov 2008 09:08:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.soacenter.com/?p=165#comment-10</guid>
		<description>Hi Miko

Please note that human skills and psychology are not just tools, marble, clay, hammer and chisel. To me proper planning, skills, habits, rules, ways of working, etc can not be replaced by software. The people are not appliances.

Probably David wanted to say that the most important is to invest efforts in good planing and the tools to be selected according to the plan...Without good plan you’ll be in hot water fast with any tool...

By the way the technology has clay that can be strong as marble and can be modeled with bare hands, probably you(like many others) use buildings made from concrete... :-)

Kamen</description>
		<content:encoded><![CDATA[<p>Hi Miko</p>
<p>Please note that human skills and psychology are not just tools, marble, clay, hammer and chisel. To me proper planning, skills, habits, rules, ways of working, etc can not be replaced by software. The people are not appliances.</p>
<p>Probably David wanted to say that the most important is to invest efforts in good planing and the tools to be selected according to the plan&#8230;Without good plan you’ll be in hot water fast with any tool&#8230;</p>
<p>By the way the technology has clay that can be strong as marble and can be modeled with bare hands, probably you(like many others) use buildings made from concrete&#8230; <img src='http://www.miko.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Kamen</p>
]]></content:encoded>
	</item>
</channel>
</rss>

