RE: Is a new firmware version a "feature"?

Subject: RE: Is a new firmware version a "feature"?
From: Beverly Robinson <beverly_robinson -at- datacard -dot- com>
To: Gene Kim-Eng <techwr -at- genek -dot- com>
Date: Fri, 9 Aug 2013 13:39:57 -0500

I understand not upgrading firmware automatically, especially in high-security environments like Kevin's (and my) customers have. All the more reason to put the emphasis on what problem each feature fixes and mentioning any required firmware as another data point to help decide whether to pursue installing the new feature.

It's a matter of emphasis: organizing by whether new firmware is required puts the emphasis on the firmware while organizing by software feature emphasizes problems solved. It just seemed to me that both organizations in Kevin's original message put the emPHAsis on the wrong sylLAble.

Beverly
-----Original Message-----
From: Gene Kim-Eng [mailto:techwr -at- genek -dot- com]
Sent: Friday, August 09, 2013 12:01 PM
To: Beverly Robinson
Cc: Techwr-l Posting; Kevin -dot- McLauchlan -at- safenet-inc -dot- com
Subject: Re: Is a new firmware version a "feature"?

The reason it matters is that not everyone installs every new firmware update. If your computer's model has been out for a few years, it's probably had a BIOS update, but do a search on "should I update my BIOS"
and you'll see that the overwhelming consensus is that you shouldn't unless a newer one fixes a problem you're having or adds something you need. Because a failed firmware update can convert most any piece of equipment into either an expensive doorstop or an expensive service call, along with expensive down time. So for every firmware update, there's someone out in installed base browsing the release notes asking "why should I want to install this?"

Gene Kim-Eng


On 8/9/2013 7:21 AM, Beverly Robinson wrote:
> I don't understand the need to categorize new features by whether they need the new firmware. If I have been waiting for a certain new feature and will start using it as soon as possible, whether that feature needs new firmware is not important.



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.

Learn more: http://bit.ly/ZeOZeQ

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


Follow-Ups:

References:
RE: Is a new firmware version a "feature"?: From: Beverly Robinson
Re: Is a new firmware version a "feature"?: From: Gene Kim-Eng

Previous by Author: RE: Is a new firmware version a "feature"?
Next by Author: RE: What to call this thing?
Previous by Thread: Re: Is a new firmware version a "feature"?
Next by Thread: RE: Is a new firmware version a "feature"?


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads