TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Best Documentation From:Peter <pnewman1 -at- home -dot- com> To:Anthony Markatos <tonymar -at- hotmail -dot- com> Date:Fri, 04 Feb 2000 18:45:38 -0500
Anthony Markatos wrote:
>
> Tony Markatos responds (to Brent Jones below):
>
> Text is a very poor means of communicating procedural informal. Text is one
> dimensional; procedures (especially those associated with complex software
> systems) are multidimensional - different things happening at the same time
> and multi-branching. Graphics are much better because they allow one to
> clearly communicate the multidimensional aspect of procedure. And as you
> have found, properly "chucked" graphics are even better.
>
> All of the above is a major reason (there are others) why writting skills
> are of RELATIVELY minor importance in technical communications.
While it is said that one picture is worth a thousand words, good
writing is paramount. The title is Technical "writing" NOT technical
"drawing." IMNVHO, when graphics become crutches for poor writing, the
user suffers.
