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: Examining proficiency of job applicants in FrameMaker
Subject:Re: Examining proficiency of job applicants in FrameMaker From:"Bonnie Granat" <bgranat -at- granatedit -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 5 Jan 2004 20:00:44 -0500
Bruce Byfield wrote:
> Quoting Catherine Arthur <carthur000 -at- sympatico -dot- ca>:
>
>>
>> I have seen an unfortunate situation where a technical writer come
>> into a company, and the writer did not have FrameMaker experience.
>> It was not required as the team felt, as many of you do, that it
can
>> be picked up quite easily. After a few months, the person was let
go
>> and another writer took over the document. The template was largely
>> unused, text was formatted without styles, numbering was all
>> hardcoded, as were all cross references. This took some time to
>> clean up, with the document to be sent to the printer the next day.
>
>> From your description, the problem wasn't that the writer didn't
have
> FrameMaker experience. Rather, the writer didn't have professional
> knowledge of word processing. If someone isn't using styles and is
> doing numbers manually (which I suppose is what you mean by
> "hardcoded"), then he or she is going to do just as badly in MS Word
> or WordPerfect.
>
> Someone who could do professional word processing might not know
> exactly how styles were set up or numbering was automated in
> FrameMaker. However, he or she would have an idea that these tools
> were available and look for them.
It's odd that it took months to find out what a supervisor should have
found out within a day or two.
And to find out the day before it was due at the printer? There's more
wrong here than the poor technical writer, it would seem.