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: Writing for the avid non-reader. From:Brett E Lee-1 <leex0096 -at- MAROON -dot- TC -dot- UMN -dot- EDU> Date:Tue, 25 Jan 1994 03:21:11 -0600
We have a great graphic artist.
We use about as many pictures as is considered politically correct.
The problem is that graphics tackle the relatively lightweight hardware
issues, including removing covers and wiring peripherals. They don't work
as well when describing complex programming procedures and 101 exceptions
to the rule.
How do you use graphics with programming procedures? Flowcharts are a
waste of my audiences time. They only want to perform, not understand. If
you consider tables to be a graphic element, there is already extensive
use of graphics even within complicated programming procedures.