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.
> Some of the comments made, including Andrew's about his chat with the CTO,
> imply that writers are talking about fonts, etc., to non-writers. Is this
> really typical? I can understand why writers would talk about such things on
> techwr-l, but I can't imagine mentioning any such thing to my CTO.
While I can remember a contract where I was the only technical writer, and I was
trying to
set up a corporate look-and-feel and thus was negotiating fonts with the head of
marketing,
most of the time the fonts and other look-and-feel issues are either inherited from
a
predecessor in the company or borrowed from some other company's style sheet.
(Remember when a lot of us started using Garamond because Apple was using it? and
when a lot of us started using wide left margins because HP and Microsoft were doing
it?)
In particular, CTOs and the like rarely get involved in font discussions. (That's
left for
endless discussions in places like this board. <g>)
I suspect Andrew was indulging in his usual hyperbole when he paraphrased the CTO,
although the gist of the objection was that writers should spend the majority of
their time
gathering information and writing, and very little time on stylistic issues such as
templates
and style sheets. I agree completely. The problem is that technical folks tend to
find little
value in process, and while I understand their point of view, I value a certain
minimum
amount of time spent defining the process and thus the expectations - it tends to
make the
subsequent execution work better. Too much time in this exercise, of course, is
likely to
raise the hackles of those like the CTO in Andrew's example. Which is one of the
reasons I
put a process discussion in contract negotiation - that way these things get ironed
out
before we start billing.
Elna Tymes
Los Trancos Systems
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY. http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by DigiPub Solutions Corp, producers of PDF 2001
Conference East, June 4-5, Baltimore/Washington D.C. area. http://www.pdfconference.com or toll-free 877/278-2131.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.