Unfortunately, many writers of technical content have other priorities. If
their work is "comprehensive", if it describes all the things it's supposed to
describe, they feel they've done their job. Never mind if the result is a
confusing assemblage of seemingly random facts, hard to follow and hard to
place in context.
Mark Walker is a poster child for this syndrome. It's pretty obvious how he
wrote Visio 2000 Bible. He made a comprehensive list of Visio features and
wrote about them one by one. Every feature, regardless of importance, gets much
the same treatment. Only a few cross references show how related features work
together. Little effort is made to describe the features clearly or concisely.
Here's an example. "There are two ways to activate and set snap and glue.
First, you can use the Snap and Glue Toolbar buttons (as shown in Figure 10-8),
or you can select Tools -> Snap & Glue to adjust settings in the Snap & Glue
dialog box. The Snap & Glue Toolbar button and dialog box are interrelated, so
a change in one also is recorded in the other. The following exercise
demonstrates the relationship...:" Then there's a lengthy demonstration of how
toolbar and dialog work. Then there's a mini-essay on when you'd use the
toolbar and when you'd use the dialog. And *then*, there's a vague, confusing
description of what the toolbar and dialog box are *for*. The whole discussion
uses up a couple of pages, but boils down to four simple statements: (1)
there's a bunch of Visio options relating to the Snap feature or the Glue
feature; (2) Two of these options enable or disable the two features; (3) the
rest of the options control the way the two features work; (4) you can set
these options one at a time (with the Snap & Glue toolbar) or all at once (with
the Snap & Glue dialog).
The reader can be excused for asking, "Jeesh, why didn't he just *say* that?"
Well, boiling complicated details down to simple descriptions is hard work. I
sometimes have to attack a concept six different ways before I'm able to
describe it in a few brief sentences. Good technical prose can be pretty
exhausting to write. It also tends to be discouraged by bosses and publishers,
who too often judge writers by the quantity of their output, not its quality.
Still, a good writer can deal with these issues. You help people understand why
fewer words often means better content. You balance work quality against
personal limitations and unavoidable deadlines. It's not easy to do all this
and still make a decent living. That's especially true if you're working
independently. But is that an excuse for short-changing your readers?
This book goes into detail that new users will be interested in as well. It explains the temples and shapes, how to edit them, how to set the properties for the page and other miscellaneous topics you need to get started. If you want to make a visual representation of some data that interacts with a spreadsheet or database, you can use this book for guidance and creative insite.