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.
---------
From: Tim Altom[SMTP:taltom -at- IQUEST -dot- NET]
> We know in advance that we'll have to top
>last year's achievement, and indeed we make it a habit to predesign so that
>we can implement tomorrow's neat stuff.
>So how have y'all approached this, if you have at all? Is today's techdoc
>department way too burdened to even predesign?
Why should we bother to predesign when we know that Microsoft is going to change the standard by next year? Seriously, I am burdened enough trying just to keep up with the HTML, SGML, RTF debate. Software documentation changes so fast that just keeping up with the tools is insane. This year I am being asked to convert everything into WinHelp and Acrobat. I am sure the industry will come up with something new next year. For me it's just another conversion.
Rebecca M. Phillips
Documentation Manager
Qronus Interactive Ltd.
Automated System Testing http://www.qronus-int.com
rebecca -at- qronus -dot- co -dot- il
