<?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"
	>
<channel>
	<title>Comments on: ARE WE JUST CRAZY WITH NEW TECHNOLOGY?</title>
	<atom:link href="http://www.previewnaples.com/blog/2007/01/05/are-we-just-getting-inundated-with-new-technology/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.previewnaples.com/blog/2007/01/05/are-we-just-getting-inundated-with-new-technology/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Sat, 22 Nov 2008 02:43:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Jackie "J P"</title>
		<link>http://www.previewnaples.com/blog/2007/01/05/are-we-just-getting-inundated-with-new-technology/#comment-18736</link>
		<dc:creator>Jackie "J P"</dc:creator>
		<pubDate>Tue, 21 Oct 2008 15:40:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.naplesrealestatevoice.com/2007/01/05/are-we-just-getting-inundated-with-new-technology/#comment-18736</guid>
		<description>"Just how far to the front of the technical leading edge should my business be?" is a very good question.  As the owner of a IT consulting firm, this is a subject on which I frequently consult.  We often jokingly refer to the absolute front of the leading edge as the "bleeding edge".  Dealing with the quirks, features (OK I mean bugs) in new technology often leaves us frustrated with the vendor.  Therefore, long ago I decided that I would never recommend that a client use anything called version 1.0.  Why?  Errors will inevitably persist through the testing phase of a product.  The vendor is actually relying on you, the first purchasers of the software, to do testing for them.  They will never admit to that, but releasing a product too soon is a lot cheaper than developing a proper test plan and hiring a staff to do the testing.  Usually by the time software has gotten to the testing phase, the budget has run out anyway.  So after being cut by the razor's edge of the bleeding once too often, we now sit back and let the gadget crazy people play with versions 1.0 and 1.1.  Then we buy version 1.3 when all the nasty bugs have been shaken out of it.  In this way we protect our client's money and budget.

Since we replace our hardware every three years, and will forever do this, the leading edge of hardware does not have the draw it once did.  We let the techincal needs of the client (most often speed and security) drive the hardware purchasing.  Storage requirements are not an issue any more.  Oh yes but we do like our toys -new phones and digital cameras - but to really make use of the full capabilities of a new device, you have got to attend on line webinars, or sit down and read the on line help undisturbed. 

 Lately we see that the difficult tasks have become easy and the simple tasks have become difficult.  This is true with Windows Vista 64 bit where we are currently on the bleeding edge.   We have Object Oriented Programming to thank for that; they don't call it OOPs for nothing.  But in general, for a mission critical need, I will buy the best and invest the resources of time and money in training.  For other needs I let the rest of the world bleed first for me.</description>
		<content:encoded><![CDATA[<p>&#8220;Just how far to the front of the technical leading edge should my business be?&#8221; is a very good question.  As the owner of a IT consulting firm, this is a subject on which I frequently consult.  We often jokingly refer to the absolute front of the leading edge as the &#8220;bleeding edge&#8221;.  Dealing with the quirks, features (OK I mean bugs) in new technology often leaves us frustrated with the vendor.  Therefore, long ago I decided that I would never recommend that a client use anything called version 1.0.  Why?  Errors will inevitably persist through the testing phase of a product.  The vendor is actually relying on you, the first purchasers of the software, to do testing for them.  They will never admit to that, but releasing a product too soon is a lot cheaper than developing a proper test plan and hiring a staff to do the testing.  Usually by the time software has gotten to the testing phase, the budget has run out anyway.  So after being cut by the razor&#8217;s edge of the bleeding once too often, we now sit back and let the gadget crazy people play with versions 1.0 and 1.1.  Then we buy version 1.3 when all the nasty bugs have been shaken out of it.  In this way we protect our client&#8217;s money and budget.</p>
<p>Since we replace our hardware every three years, and will forever do this, the leading edge of hardware does not have the draw it once did.  We let the techincal needs of the client (most often speed and security) drive the hardware purchasing.  Storage requirements are not an issue any more.  Oh yes but we do like our toys -new phones and digital cameras - but to really make use of the full capabilities of a new device, you have got to attend on line webinars, or sit down and read the on line help undisturbed. </p>
<p> Lately we see that the difficult tasks have become easy and the simple tasks have become difficult.  This is true with Windows Vista 64 bit where we are currently on the bleeding edge.   We have Object Oriented Programming to thank for that; they don&#8217;t call it OOPs for nothing.  But in general, for a mission critical need, I will buy the best and invest the resources of time and money in training.  For other needs I let the rest of the world bleed first for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 2fa8650d69ba5aa0350ecd6788706414</title>
		<link>http://www.previewnaples.com/blog/2007/01/05/are-we-just-getting-inundated-with-new-technology/#comment-1983</link>
		<dc:creator>2fa8650d69ba5aa0350ecd6788706414</dc:creator>
		<pubDate>Thu, 05 Jul 2007 05:51:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.naplesrealestatevoice.com/2007/01/05/are-we-just-getting-inundated-with-new-technology/#comment-1983</guid>
		<description>&lt;strong&gt;2fa8650d69ba5aa0350ecd6788706414...&lt;/strong&gt;

2fa8650d69ba5aa0350ecd6788706414...</description>
		<content:encoded><![CDATA[<p><strong>2fa8650d69ba5aa0350ecd6788706414&#8230;</strong></p>
<p>2fa8650d69ba5aa0350ecd6788706414&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
