Checking code (was: Software engineer tech. writers? )

[Chris Borokowski]

One of the reasons I think technical writers should branch out into
usability is that such things often go unnoticed, and fixing them is a
skill that directly relates to the skillset of communicating with
users. Users need consistency, not "creativity" in randomly naming
buttons, commands, and so on. I see inconsistency quite a bit, and most
of my comments returned to engineers are fixes in that area.

--- "Martinek, Carla" <CMartinek at zebra.com> wrote:

> Years ago I was documenting a program for a mobile radio computer. 
> As I
> went through the program, I started noticing that the buttons used
> for
> various functions (think DOS application screens) varied from screen
> to
> screen.  For example, Print might be F6 on one screen, but F8 on
> another, and so on. 


http://technical-writing.dionysius.com/
technical writing | consulting | development


       
____________________________________________________________________________________
Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.
http://farechase.yahoo.com/