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 02:13 PM 03/11/2000 -0800, R Greenberg wrote:
>I'm going to be job-hunting soon, so I'm in the
>process of preparation. I have a few pieces of writing
>from my current job that I think would be great for my
>portfolio. Trouble is, one of them is 20 pages long,
>another is 28, and the third is 10 pages. From what
>I've heard, this is much too long - that the average
>portfolio shows only 3 or 4 pages of each piece of
>writing. However, I would like to show the entirety of each
>piece because I want to show structure and
>organization as well as the writing itself. The person
>looking at it wouldn't be expected to read the entire
>thing, but rather to skim most of it, observing the
>general pattern and maybe reading small parts of it in
>depth to get a sense of the writing itself.
Personally, I would show them in their entirety. When I changed jobs, I
didn't know any better, so brought complete examples with me, and everyone
seemed very impressed (primarily because I'm also the developer, and most
programmers/developers don't do their own writing). I think it really
Obviously, interviewers didn't sit reading them from cover-to-cover -- but,
having an entire piece enabled them to skim over certain segments and
confirm that they were clear and concise.