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.
>I documented the number
>of pages I printed and the time I spent waiting at the network printer. My
>boss funded an individual printer for me based on my figures. Food for
>thought...
On two completely separate projects in the last three years, my group has
demonstrated that technical writers tend to tie up a print queue so badly
that the others complain. In both cases, project management started out
by insisting that we could use an existing group printer. Heh. The minute
we started trying to print bitmaps (screen dumps) we tied up the queue
somethin' awful! On one of these contracts, our simple <g> demands
brought the network queue down five times in one afternoon, and one of us
had to stay until midnight to get out a print job that was due the next
morning. Since they were paying us by the hour, they quickly computed
the costs of our time babysitting a print queue, vs. the cost of renting
our own printer, and opted for the latter.
