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.
Unfortunately, Sarah's rant and many of the subsequent follow-ups
underscore once more the lack of respect our profession receives from
those outside.
Yeah, yeah - many, many of us have overcome this sorry state of affairs
and maintain good and proper working relationships with our
subjectmatter experts (SME's).
But the mere fact that newcomers or relative newbies experience this
problem shows how little consideration is given to those who explain to
the great unwashed HOW and WHY things work.
We're considered "glorified secretaries" by some (yep, I've actually
heard that one), unskilled labor by others, and pretty much an
afterthought by those who themselves practically DEMAND a genuflection
upon entering their office or cubicle.
Nobody disses attorneys, MD's and various other professionals. So what
should WE do? Wear a uniform? What should it consist of? (I mean, "Of
what should it consist?"). Probably a THICK, THICK outer material that
repels criticism and sarcastic jabs, but still presents a pleasing,
attractive appearance.
Let's face it, it is and will always be an uphill battle - really an
occupational hazard - to be treated so negligently.
The answer, everyone's on their own.
Those who have been able to attain and hold onto truly professional
working relationships will breathe purer air and hopefully throw tips
and tricks to those of us still down in the mineshafts trying to get up
and out.
-- Kenpo
(In Atlanta, on a crappy, drizzly Wednesday)
-----Original Message-----
From: techwr-l-bounces+poshedlyk=polysius -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+poshedlyk=polysius -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf Of Sarah Bouchier
Sent: Tuesday, September 12, 2006 11:13 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Gnaargh! Or, I Am Not Psychic
This will, I suspect, be a familiar rant to most of you.
I've just discovered that, shortly after both I and the client went
through and checked my company's user manual and online help against the
product, the development team made some major changes to the UI without
telling the doc team.
Normally I'd have picked this up through the paranoiac (though
justified, I feel!) checking I do anytime I have a few minutes spare,
but what with it being the last few days before the release deadline I
was working ten hour lunchless days as it was, and I +really+ didn't
have the spare time to go through the entire product to see if anything
had changed.
Unfortunately, there's scarcely a process here, never mind one that
includes the technical authors. The closest thing is the bug tracking
system, but apparently most of those changes didn't go through it (and
even if they had, I've yet to train the developers to assign bugs to
documentation after fixing).
What is the best process you've ever worked with (or dreamed of) that
enables technical authors to find out about changes/new projects etc
before the very last minute is past?
The prize for the best answer is me doing my damnedest to implement it
here :)
S.
-----------------------------------------
Sarah Bouchier
Technical Author
This e-mail message and any attachment contains private
and confidential information and is intended for the addressee only. If you are not the intended recipient (or responsible
for delivery of the message to such person), please do not read, copy, use or disclose this communication to others.
If you have received this message in error, please notify the sender by replying to this message, and then delete it from your system. Thank you.
____________________
Polysius Corp.
Atlanta, Ga. USA http://www.PolysiusUSA.com
Voice: 770-850-2000
Main Fax: 770-955-8789
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-