<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Excessive Tech meets Excessive Force</title>
	<link>http://www.dancres.org/blitzblog/2007/04/23/excessive-tech-meets-excessive-force/</link>
	<description></description>
	<pubDate>Sat, 05 Jul 2008 08:35:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Dan Creswell</title>
		<link>http://www.dancres.org/blitzblog/2007/04/23/excessive-tech-meets-excessive-force/#comment-628</link>
		<dc:creator>Dan Creswell</dc:creator>
		<pubDate>Mon, 30 Apr 2007 12:26:21 +0000</pubDate>
		<guid>http://www.dancres.org/blitzblog/2007/04/23/excessive-tech-meets-excessive-force/#comment-628</guid>
		<description>Udi,

Yep although making the helicopter aware of position will require comms from the unit albeit perhaps a single burst though in at least some combat situations the pick-up point is fluid due to pursuit by enemy forces which thus requires repeated bursts.

And in fact at least special forces already carry such equipment which they can enable at the point of distress giving a good balance between risk of exposure and recoverability.</description>
		<content:encoded><![CDATA[<p>Udi,</p>
<p>Yep although making the helicopter aware of position will require comms from the unit albeit perhaps a single burst though in at least some combat situations the pick-up point is fluid due to pursuit by enemy forces which thus requires repeated bursts.</p>
<p>And in fact at least special forces already carry such equipment which they can enable at the point of distress giving a good balance between risk of exposure and recoverability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Udi Dahan</title>
		<link>http://www.dancres.org/blitzblog/2007/04/23/excessive-tech-meets-excessive-force/#comment-627</link>
		<dc:creator>Udi Dahan</dc:creator>
		<pubDate>Mon, 30 Apr 2007 11:51:20 +0000</pubDate>
		<guid>http://www.dancres.org/blitzblog/2007/04/23/excessive-tech-meets-excessive-force/#comment-627</guid>
		<description>Consider the case where a helicopter pilot needs to evacuate a unit. Knowing where the unit is, without needing to communicate with them - which itself might lead to their exposure, is extremely valuable.

Although I agree that within the unit itself the relevance of the technology is more limited.</description>
		<content:encoded><![CDATA[<p>Consider the case where a helicopter pilot needs to evacuate a unit. Knowing where the unit is, without needing to communicate with them - which itself might lead to their exposure, is extremely valuable.</p>
<p>Although I agree that within the unit itself the relevance of the technology is more limited.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Creswell</title>
		<link>http://www.dancres.org/blitzblog/2007/04/23/excessive-tech-meets-excessive-force/#comment-604</link>
		<dc:creator>Dan Creswell</dc:creator>
		<pubDate>Tue, 24 Apr 2007 07:52:21 +0000</pubDate>
		<guid>http://www.dancres.org/blitzblog/2007/04/23/excessive-tech-meets-excessive-force/#comment-604</guid>
		<description>Deployment into the field is acceptable if up until now you've been successful which is not the case for the military tech above.  Certainly in terms of close quarter battle tactics, trusting your team to be in the right place at the right time appears absolutely necessary as you need all your senses deployed searching for the enemy and responding to their actions as quickly as possible.

In the case of Java one can argue that deployment is the only way to test effectiveness but:

(1)  There should be some plan for removing features that fail in such a deployment - deprecation doesn't count as it takes too long.  I'm talking rollback for want of a better term.

(2)  There should be some appropriate datapoints to justify the deployment - too many times we accept subjective arguments backed by zero critical thinking which for our profession is surely unacceptable.</description>
		<content:encoded><![CDATA[<p>Deployment into the field is acceptable if up until now you&#8217;ve been successful which is not the case for the military tech above.  Certainly in terms of close quarter battle tactics, trusting your team to be in the right place at the right time appears absolutely necessary as you need all your senses deployed searching for the enemy and responding to their actions as quickly as possible.</p>
<p>In the case of Java one can argue that deployment is the only way to test effectiveness but:</p>
<p>(1)  There should be some plan for removing features that fail in such a deployment - deprecation doesn&#8217;t count as it takes too long.  I&#8217;m talking rollback for want of a better term.</p>
<p>(2)  There should be some appropriate datapoints to justify the deployment - too many times we accept subjective arguments backed by zero critical thinking which for our profession is surely unacceptable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fabrizio Giudici</title>
		<link>http://www.dancres.org/blitzblog/2007/04/23/excessive-tech-meets-excessive-force/#comment-603</link>
		<dc:creator>Fabrizio Giudici</dc:creator>
		<pubDate>Mon, 23 Apr 2007 21:30:53 +0000</pubDate>
		<guid>http://www.dancres.org/blitzblog/2007/04/23/excessive-tech-meets-excessive-force/#comment-603</guid>
		<description>Looks like the debate "new features in the Java language vs architecture and process management". OTOH they have the technology, it must be deployed on the field for testing sooner or later. At this stage it's the only definite way to learn whether things are wrong or must be improved.</description>
		<content:encoded><![CDATA[<p>Looks like the debate &#8220;new features in the Java language vs architecture and process management&#8221;. OTOH they have the technology, it must be deployed on the field for testing sooner or later. At this stage it&#8217;s the only definite way to learn whether things are wrong or must be improved.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
