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.
At 09:40 AM 03/15/2000 -0500, Kat Nagel wrote:
>I *have* gotten calls from interviewing managers who recognized
>something I had written in someone else's portfolio. It happens.
I've had similar experiences ... Interviewers would ask detailed, in-depth
questions --
and subsequently tell me that I should be aware of the fact that other
people were putting their names on my work (which my answers very clearly
proved was entirely mine).
The biggest problem is that many, many interviewers do not know what to ask
or look for -- so are very easily snowed. I've been in situations where
company purchased complex, expensive applications which were hard-coded,
and which did not include the source code -- with the result that, if any
of our 10,000 employees so much as got a new printer, the programmer had to
be re-hired at a very hefty rate.
Others paid for the source code, but didn't have anyone knowledgeable look
at it -- with the result that all procs, vars, etc. were named "A1", "A2",
etc., with no hint as to what they did. Still others incorporated
third-party products (again, without source code) -- and, when the third
party went belly up, so did the entire system, which could no longer run
with the newer version of DOS, Windows, Word, or whatever.
I wish that someone would teach interviewers what to look for, and what to
ask <sigh>.
"Scottie"
(The Scottish Terrier Lover)
