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.
Subject:RE: A Need to fill the matrix From:Diane Brennan <dalaine00 -at- yahoo -dot- com> To:'Bill Swallow' <techcommdood -at- gmail -dot- com>, Lauren <lauren -at- writeco -dot- net> Date:Fri, 23 Jan 2009 14:32:06 -0800 (PST)
In the Seattle area this position is called a programmer writer but I think that position title may not have migrated to other areas. I worked as a programmer writer for seven years so you'll have to trust me on this.
I may be making assumptions about the position requiring the writer to write sample scripts because of my work background. To me, when you are dealing with applications writing to databases there is some SQL scripting involved. But that may not necessarily be the case. Usually if the writer is required to do product testing, it will be part of the job description. That's why I assumed that the recruiter was thinking that the writer would need to write his own scripts in order to test or create procedures for writing to the database. So "writing a test script" would be, in the mind of the recruiter, a skill that would be required for this particular task.
You really need to ask the recruiter why the writer needs this skill.
--- On Fri, 1/23/09, Lauren <lauren -at- writeco -dot- net> wrote:
From: Lauren <lauren -at- writeco -dot- net>
Subject: RE: A Need to fill the matrix
To: "'Bill Swallow'" <techcommdood -at- gmail -dot- com>, dalaine00 -at- yahoo -dot- com
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Friday, January 23, 2009, 1:17 PM
I've written test scripts. I needed to interview programmers and to learn
about the application or hardware, though. Whatever I was documenting. The
job title was still Technical Writer. I've never heard of "Programmer
Writer," but I have worked as a Technical Writer and I have had assorted
application development titles. The test script writer always fell under
the technical writer umbrella for me, but it has been awhile since I have
> From: Bill Swallow
> > This position is actually a programmer writer and
> programmer writers do write code and script examples.
> Where did you see that? I don't see it anywhere. And test scripts are
> different from examples.
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-