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 have had good luck writing on the test system. I save often and keep
backups to boot. Yup, crashes happen. Oh well. Log it and move on <vbg>. It
is interesting that you had beta software crash hard near *your* deadline.
Seems maybe the beta program ought to be extended and your deadline move
accordingly ;?P
People do accept buggy software, I know I do. I have never worked for a
software company that thought it was releasing bug-free software <g>.
Running the beta software on a writer's system seems like a pretty good QA
test, doesn't it <g>.
Best regards,
Sean
sean -at- quodata -dot- com
P.S. Isn't weeping in your job description????
> -----Original Message-----
> From: Elizabeth Ross [SMTP:beth -at- vcubed -dot- com]
>
> I have two systems on my desk: one for testing and one for writing the
> manual. I tried to do both on one system, but some beta software crashed
> it
> one day quite near my deadline.
>
> Never, ever, ever write your documentation on your test system. Bad things
> will happen eventually and you will weep.
