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.
Subject:Servers vs. local From:"Arlen P. Walker" <Arlen -dot- P -dot- Walker -at- JCI -dot- COM> Date:Fri, 4 Nov 1994 11:42:00 -0500
The recent discussion on FrameMaker backups brought a thought to mind. One of
the posters took it as an article of faith that you never work on files on the
server. You first copy them down locally and work on them, then copy them back
up. There's a group here who see the copying as wasted effort, and simply work
off the server. (There's the complete previous edition, and then the "work in
progress".) That way they never have a situation where the server does not
contain the most recent copy.
I'm assuming all version control systems force copying down to local discs. So
for those of you working in networked environments and not using version control
systems:
a) Do you work on the server?
b) What do you see as the *best point* in favor of the way you're doing it?
Have fun,
Arlen
Arlen -dot- P -dot- Walker -at- JCI -dot- Com
----------------------------------------------
In God we trust; all others must provide data.
----------------------------------------------
