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.
Lets be honest about MOST tech writers and MOST developers:
MOST tech writers should stay away from commenting on
interface design because they have never developed a
GUI and they don't know enough about what goes on behind
the form/screen/window to make a worthwhile suggestion.
MOST developers have trouble spelling/aligning/standardizing
their way out of the proverbial paper bag when in comes
to GUI construction.
Obviously, as with anything else, there are exceptions to
the rule. I don't see the need to get flustered over editing
a GUI, though--if you are a tech writer and you have the GUI
standard and it is not being followed, edit away. I routinely
capture screens and correct spelling, draw lines to show
misaligned controls, and highlight inconsistencies. If you
know what you are doing (I am also a developer), what is the
big deal?
Graham R. Tillotson, Senior Consultant
Whittman-Hart, Inc.
300 N. Elizabeth
Chicago, IL 60607
