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.
Mr. Czekalski makes several good points, though he seems a little paranoid
with regards to his third rule below. Often during interviews I don't have
enough time to seriously read or examine a portfolio sample. If the writer
is not willing to leave me material (or a copy of the material) how can I
adequately evaluate their skills? If the work is propreitary, why bring it
to the interview at all?
Furthermore, it is worth mentioning that there is plenty of content being
developed that is not in the least bit proprietary. I mostly write end-user
materials, and thus 95% of my work is accessable to anyone who wants to see
it. Just my two cents. DB.
From: Jason A. Czekalski [mailto:topsidefarm -at- mva -dot- net]
Sent: Monday, March 13, 2000 1:57 PM
Subject: Re: portfolio questions
There are some rules for using such work for portfolio purposes:
First, bookmark the specific sections you want to show. Nothing looks
worse than fumbling through a manual you wrote.
Second, do not show sections of the work that might be proprietary.
Third, the manual is for show-and-tell only. NEVER leave a copy with a
prospective client. Maintain control of any portfolio manual at all