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.
Re: Not too technical, still OK (was: Desperately seeking employment)
Subject:Re: Not too technical, still OK (was: Desperately seeking employment) From:Sybille Sterk <sybille -at- BOFFIN -dot- BEYOND2000 -dot- CO -dot- UK> Date:Wed, 14 Jul 1999 11:06:02 +0100
I agree, in-depth technical knowledge is quite often not necessary. I am
working on projects that might require experience (possibly a degree) not
just in technical areas but also in Cytogenetics, Materials science,
programming and whatnot, however, those sections of my documentation I
don't know much (or nothing at all) about, I just ask one of the
specialists either to write a brief outline for me or just pester them
until I have all the answers I need to write it myself.
Generally, I do think a writer should be able to write about anything at
all, BUT in some instances he/she will obviously need assistance. You can't
expect every technical writer to have in-depth knowledge about everything,
but I think you can expect a technical writer to be able to acquire the
necessary knowledge. This of course needs an employer who is aware of this
and prepared to supply the assistance.
Sybille
Sybille Sterk
Technical Author and Translator (German)
email: sybille -at- boffin -dot- beyond2000 -dot- co -dot- uk
