Re: Task-based versus UI-based documentation

Subject: Re: Task-based versus UI-based documentation
From: John G <john -at- garisons -dot- com>
To: "Lippincott, Richard" <RLippincott -at- as-e -dot- com>
Date: Thu, 7 Aug 2014 11:30:07 -0400

It's all about the mental gymnastics required to assimilate the complex
vagaries of a software system vs. the physical ability to touch, feel, plug
in, and use a hardware component.

In software you have to do more ground preparation for users as a lot of
what needs explaining requires the user to "get" some concept or behavior.
I have found that's less onerous when documenting hardware.

Software, IMHO, does not really "exist". Sure, it's positive and negative
0s and 1s on a whirling disk, but that's not really existence. What it is
is a series of rules and behaviors - click this or enter that and something
somewhere else changes as a result (and frequently changes in a way that it
not immediately apparent). That's different than physically pushing or
connecting this and you see/feel this happen.

But hey - I was a philosophy major, and I have to say I'm using the same
skills I learned when analyzing Kant's Phenomonology so that I can justify
it all ...

My 2Â,

JG

On Thu, Aug 7, 2014 at 11:16 AM, Lippincott, Richard <RLippincott -at- as-e -dot- com>
wrote:

>
> Hardware writing is pretty much like writing about software, just that it
> hurts more when you drop the actual product on your foot.
>
>

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l

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

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:
Task-based versus UI-based documentation: From: Cardimon, Craig
Re: Task-based versus UI-based documentation: From: Julie Stickler
RE: Task-based versus UI-based documentation: From: Lippincott, Richard

Previous by Author: Re: Task-based versus UI-based documentation
Next by Author: Re: What folks today don't know...!
Previous by Thread: RE: Task-based versus UI-based documentation
Next by Thread: RE: Task-based versus UI-based documentation


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


Sponsored Ads