<?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 Combat Consulting</title>
	<atom:link href="http://www.combatconsulting.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.combatconsulting.com</link>
	<description>Musings on getting the impossible done in hostile operational environments</description>
	<lastBuildDate>Wed, 02 Nov 2011 20:45:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>Comment on Contact Us by Michael Foster</title>
		<link>http://www.combatconsulting.com/contact/comment-page-1/#comment-701</link>
		<dc:creator>Michael Foster</dc:creator>
		<pubDate>Wed, 02 Nov 2011 20:45:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.combatconsultancy.com/?page_id=55#comment-701</guid>
		<description>The beginning of your web page is incorrect.  Unfortunely, Colonel Boyd was never promoted to general in the U. S. Air Force.</description>
		<content:encoded><![CDATA[<p>The beginning of your web page is incorrect.  Unfortunely, Colonel Boyd was never promoted to general in the U. S. Air Force.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taleb&#039;s Black Swan Glossary by A Few Random Thoughts On Waves &#124; Connect the Dots</title>
		<link>http://www.combatconsulting.com/talebs-black-swan-glossary/comment-page-1/#comment-463</link>
		<dc:creator>A Few Random Thoughts On Waves &#124; Connect the Dots</dc:creator>
		<pubDate>Mon, 28 Feb 2011 09:38:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.combatconsulting.com/talebs-black-swan-glossary#comment-463</guid>
		<description>[...] look for a pattern, a trend. Nothing terrible here, since it&#8217;s a retrospective analysis (aka narrative fallacy). Troubles come when we want to predict the future: we tend to rely too much on data, trends and [...]</description>
		<content:encoded><![CDATA[<p>[...] look for a pattern, a trend. Nothing terrible here, since it&#8217;s a retrospective analysis (aka narrative fallacy). Troubles come when we want to predict the future: we tend to rely too much on data, trends and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Shadow IT via the Cloud by Simon Wardley</title>
		<link>http://www.combatconsulting.com/shadow-it-via-the-cloud/comment-page-1/#comment-198</link>
		<dc:creator>Simon Wardley</dc:creator>
		<pubDate>Mon, 06 Dec 2010 14:22:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.combatconsulting.com/?p=477#comment-198</guid>
		<description>Thank you for the kind comment, much appreciated.

The point about Jevons&#039; paradox, is that all organisations are in competition with others and whilst cloud will reduce IT expenditure if our workloads stay the same, the result of the competition, the backlog of unmet demand and the increased rates of innovation is that we will just end up doing more stuff. You&#039;re spot on with that.

On that note, it&#039;s no different to Moore&#039;s law. Whilst a $1000 will buy you considerably more computing resources today than in 1980, this doesn&#039;t mean our IT budgets have reduced by a corresponding amount. Quite the opposite, we&#039;ve ended up doing more.

As for the human constraints, as we move forwards we&#039;re likely to end up building higher order systems (i.e. think of mashups and developing on web platforms) with the underlying systems become stable and less visible (but no less essential) components. This is a normal effect.

The result is that we will develop at much faster rates tomorrow, in much the same way that development today is much faster than when I started back in the 80&#039;s (due to underlying stable components like databases, frameworks, web services etc). The systems today are unimaginably complex and built at lightning speeds when considered in the light of programming in the 80&#039;s.

We noticed this with one of the first PaaS offerings, Zimki in 2005/06. The speed of development became ridiculously fast, with entire new concepts being released live on the web in under an hour. Of course, this panoply of innovation consumed ever more underlying compute resources.

Will cloud reduce IT expenditure? No more than Moore&#039;s law did.

Will cloud get rid of sys-admins? Not even a massive increase in capabilities &amp; automation due to orchestration tools is likely to lead to a reduction in sys-admins due to the explosion in scale and use of ephemeral architectures.

Will cloud be green? On a per unit basis it&#039;ll be more efficient but you&#039;ll end up consuming vastly more units.

The myths and misconceptions about cloud are a long tale of forgotten wisdom.</description>
		<content:encoded><![CDATA[<p>Thank you for the kind comment, much appreciated.</p>
<p>The point about Jevons&#8217; paradox, is that all organisations are in competition with others and whilst cloud will reduce IT expenditure if our workloads stay the same, the result of the competition, the backlog of unmet demand and the increased rates of innovation is that we will just end up doing more stuff. You&#8217;re spot on with that.</p>
<p>On that note, it&#8217;s no different to Moore&#8217;s law. Whilst a $1000 will buy you considerably more computing resources today than in 1980, this doesn&#8217;t mean our IT budgets have reduced by a corresponding amount. Quite the opposite, we&#8217;ve ended up doing more.</p>
<p>As for the human constraints, as we move forwards we&#8217;re likely to end up building higher order systems (i.e. think of mashups and developing on web platforms) with the underlying systems become stable and less visible (but no less essential) components. This is a normal effect.</p>
<p>The result is that we will develop at much faster rates tomorrow, in much the same way that development today is much faster than when I started back in the 80&#8242;s (due to underlying stable components like databases, frameworks, web services etc). The systems today are unimaginably complex and built at lightning speeds when considered in the light of programming in the 80&#8242;s.</p>
<p>We noticed this with one of the first PaaS offerings, Zimki in 2005/06. The speed of development became ridiculously fast, with entire new concepts being released live on the web in under an hour. Of course, this panoply of innovation consumed ever more underlying compute resources.</p>
<p>Will cloud reduce IT expenditure? No more than Moore&#8217;s law did.</p>
<p>Will cloud get rid of sys-admins? Not even a massive increase in capabilities &amp; automation due to orchestration tools is likely to lead to a reduction in sys-admins due to the explosion in scale and use of ephemeral architectures.</p>
<p>Will cloud be green? On a per unit basis it&#8217;ll be more efficient but you&#8217;ll end up consuming vastly more units.</p>
<p>The myths and misconceptions about cloud are a long tale of forgotten wisdom.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Divvy and Cinch by Mr. Oak</title>
		<link>http://www.combatconsulting.com/divvy-and-cinch/comment-page-1/#comment-197</link>
		<dc:creator>Mr. Oak</dc:creator>
		<pubDate>Sun, 05 Dec 2010 22:56:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.combatconsulting.com/divvy-and-cinch/#comment-197</guid>
		<description>I like the article, but another alternative is Size Up, from the makers of Cinch.  It&#039;s probably the most granular window size manager on Mac OS X, IMO.

http://www.irradiatedsoftware.com/sizeup/</description>
		<content:encoded><![CDATA[<p>I like the article, but another alternative is Size Up, from the makers of Cinch.  It&#8217;s probably the most granular window size manager on Mac OS X, IMO.</p>
<p><a href="http://www.irradiatedsoftware.com/sizeup/" rel="nofollow">http://www.irradiatedsoftware.com/sizeup/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Shadow IT via the Cloud by Bernard Golden</title>
		<link>http://www.combatconsulting.com/shadow-it-via-the-cloud/comment-page-1/#comment-154</link>
		<dc:creator>Bernard Golden</dc:creator>
		<pubDate>Fri, 22 Oct 2010 17:24:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.combatconsulting.com/?p=477#comment-154</guid>
		<description>Hey, thanks for the shout out!</description>
		<content:encoded><![CDATA[<p>Hey, thanks for the shout out!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Drucker and Goldratt Concept Map by Jeff McNeill</title>
		<link>http://www.combatconsulting.com/drucker-and-goldratt-concept-map/comment-page-1/#comment-104</link>
		<dc:creator>Jeff McNeill</dc:creator>
		<pubDate>Fri, 03 Sep 2010 14:17:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.combatconsulting.com/?p=455#comment-104</guid>
		<description>Actually, it was done using IHMC Cmap Lite, which is a true concept mapping application (vs. a mind map tool). Happy you found the document useful.

Cheers,
Jeff</description>
		<content:encoded><![CDATA[<p>Actually, it was done using IHMC Cmap Lite, which is a true concept mapping application (vs. a mind map tool). Happy you found the document useful.</p>
<p>Cheers,<br />
Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taleb&#039;s Black Swan Glossary by A Few Random Thoughts On Waves &#124; Personal Patterns</title>
		<link>http://www.combatconsulting.com/talebs-black-swan-glossary/comment-page-1/#comment-69</link>
		<dc:creator>A Few Random Thoughts On Waves &#124; Personal Patterns</dc:creator>
		<pubDate>Sat, 10 Jul 2010 15:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.combatconsulting.com/talebs-black-swan-glossary#comment-69</guid>
		<description>[...] look for a pattern, a trend. Nothing terrible here, since it&#8217;s a retrospective analysis (aka narrative fallacy). Troubles come when we want to predict the future: we tend to rely too much on data, trends and [...]</description>
		<content:encoded><![CDATA[<p>[...] look for a pattern, a trend. Nothing terrible here, since it&#8217;s a retrospective analysis (aka narrative fallacy). Troubles come when we want to predict the future: we tend to rely too much on data, trends and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 50 more ways to improve your business by Dejan</title>
		<link>http://www.combatconsulting.com/50-more-ways-to-improve-your-business/comment-page-1/#comment-54</link>
		<dc:creator>Dejan</dc:creator>
		<pubDate>Mon, 08 Feb 2010 23:20:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.combatconsulting.com/?p=432#comment-54</guid>
		<description>Very interesting and true reading! Glad that I found this.</description>
		<content:encoded><![CDATA[<p>Very interesting and true reading! Glad that I found this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Design Thinking by jonathan</title>
		<link>http://www.combatconsulting.com/design-thinking/comment-page-1/#comment-53</link>
		<dc:creator>jonathan</dc:creator>
		<pubDate>Tue, 26 Jan 2010 15:54:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.combatconsulting.com/design-thinking/#comment-53</guid>
		<description>Jason, as the man who introduced me to GTD it is fitting that you reminded me of the Natural Planning Model, a modified version of which we use operationally every day. 

Its great to see you poking around these parts. Please come by more often! 

I like the Crystal Garden Creativity method too. Problem is that I tend to supersaturate, grow my crystal, but then mourn the loss of every lopped off weaker connection.</description>
		<content:encoded><![CDATA[<p>Jason, as the man who introduced me to GTD it is fitting that you reminded me of the Natural Planning Model, a modified version of which we use operationally every day. </p>
<p>Its great to see you poking around these parts. Please come by more often! </p>
<p>I like the Crystal Garden Creativity method too. Problem is that I tend to supersaturate, grow my crystal, but then mourn the loss of every lopped off weaker connection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Design Thinking by Jason Bates</title>
		<link>http://www.combatconsulting.com/design-thinking/comment-page-1/#comment-52</link>
		<dc:creator>Jason Bates</dc:creator>
		<pubDate>Tue, 26 Jan 2010 15:47:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.combatconsulting.com/design-thinking/#comment-52</guid>
		<description>Hey JD, 

You might also want to add David Allen&#039;s Natural Planning Model into the mix
Which is interesting in that it highlights &#039;visioning&#039; as a step rather than some of the more emergent steps in the other methods.... maybe due to the fact that the framework isn&#039;t just for solving discrete problems, but creating positive outcomes too.

   1. Defining purpose and principles
   2. Outcome visioning
   3. Brainstorming
   4. Organizing
   5. Identifying next actions

And then there is always my &#039;Crystal Garden Creativity&#039; model to throw in the mix for something very left field.

1. Create a supersaturated solution
2. Dip a single crystal in 
3. Allow to crystallize for a period of time
4. Harvest the crystal / cut the weaker connections

Cheers,

Jasina</description>
		<content:encoded><![CDATA[<p>Hey JD, </p>
<p>You might also want to add David Allen&#8217;s Natural Planning Model into the mix<br />
Which is interesting in that it highlights &#8216;visioning&#8217; as a step rather than some of the more emergent steps in the other methods&#8230;. maybe due to the fact that the framework isn&#8217;t just for solving discrete problems, but creating positive outcomes too.</p>
<p>   1. Defining purpose and principles<br />
   2. Outcome visioning<br />
   3. Brainstorming<br />
   4. Organizing<br />
   5. Identifying next actions</p>
<p>And then there is always my &#8216;Crystal Garden Creativity&#8217; model to throw in the mix for something very left field.</p>
<p>1. Create a supersaturated solution<br />
2. Dip a single crystal in<br />
3. Allow to crystallize for a period of time<br />
4. Harvest the crystal / cut the weaker connections</p>
<p>Cheers,</p>
<p>Jasina</p>
]]></content:encoded>
	</item>
</channel>
</rss>

