Re: H/W v S/W difficulty

[Richard Lippincott <rlippinc -at- BEV -dot- ETN -dot- COM>]

RoMay said:

>I've stayed out of this one until now, but the whole argument seems
>pointless to me.  Regardless of what you are writing, there are bound to
>be challenges:  difficulties with access, knowledge of the topic to be
>learned, language issues to be addressed and so on.  Since we each bring to
>the task only the experiences and knowledge we already have, each faces unique
>problems--and personal viewpoints relative to them.  "My job is really
>tough" is true for most of us in one aspect or another.

>IMHP, what counts most is showing consideration for the truth of this for
>our fellow writers, regardless of what they are writing.  And recognizing
>that what may be easier for us may not be easy for someone else because
>their experience has given them a different set of knowledge parameters.

RoMay understands the whole point.

The original question was posted last Friday, and I jumped in saying "Hardware
writing is tougher."  Of course, I did this -knowing- that the majority of
people on this list are not hardware writers. And those that did responde to
my comments made very good points.

If you read back through the thread, you'll notice that on occasion I'd throw
in a comment to the effect of "Of course, I'm sure any of us could handle the
challenge of the other type of writing..."  In other words, they both can be
tough at times.  Both have their easy moments as well.

Enough of that. I've got some software documentation to write.

Rick Lippincott
Eaton Semiconductor
rlippinc -at- bev -dot- etn -dot- com