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.
>If what I think is right, you shouldn't be working on files from the file
>server. You should copy files to your own disk or file system to work
>on. After you're done, you may return the file to the server.
I disagree. Unless you've got a good version control system, this is a
recipe for losing data. (This is based on several years of experience
in database tech support.)
The only good reason for putting the files local with a backup to the
server is performance.
--
--- Aahz (@netcom.com)
Hugs and backrubs -- I break Rule 6
Androgynous kinky vanilla queer het
Seeking job in Silicon Valley doing tech writing or database tech support.
Prefer Unix-oriented position. Send e-mail for resume.
