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.
At 06:17 AM 04/27/2000 , Alison Tartt wrote:
>I'm the lone writer...No one will be making
>changes to my material except me ...A
>couple of members of the development
>team want me to work through Visual
>Source Safe, which is on Server B ...
Unless I'm missing something, Visual Source Safe won't be necessary since
you are the only person modifying these particular files.
Source Safe is invaluable for developers working on the same project. (The
alternative, as I recall all too vividly from the days before such tools
became available, is to have developers overwriting each other's code.)
However, I've never heard of using it when only one person is working on a
project or particular stand-alone aspect of the project.
