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:Re: Git [was RE: Windows VM on Mac ?] From:"Elisa R. Sawyer" <elisawyer -at- gmail -dot- com> To:Peter Neilson <neilson -at- windstream -dot- net> Date:Tue, 21 Mar 2017 12:59:46 -0700
No version control system can make up for situations where people are
inconsiderately over-writing files or where chaos reigns. As a long-term
contractor, I am fortunate to have worked on teams of writers where, even
with no version control, we didn't cause each other problems. I have also
seen situations where even the best version control system could not make
up for bad habits.
-Elisa
On Tue, Mar 21, 2017 at 12:10 PM, Peter Neilson <neilson -at- windstream -dot- net>
wrote:
> On Tue, 21 Mar 2017 14:03:17 -0400, <mbaker -at- analecta -dot- com> wrote:
>
> I think much of this comes down to the issue of loose coupling vs tight
>> coupling. Good coding practice is to create loosely coupled systems.
>>
>
> Yes, loose coupling and defined interfaces is best. Years ago I was coding
> in assembler and Fortran, and there were pieces of assembler code marked
> "DO NOT MOVE THIS CODE" and other pieces that should have been so marked,
> but weren't. The only saving grace was the source control--a locked cabinet
> of drawers where I stored the punched cards.
>
> But if you take a very tightly coupled information set with tightly coupled
>> source file and throw it at a distributed source control system without
>> changing anybody's habits, you are asking for pain and suffering.
>>
>
> Indeed. I have been put into a situation where we all were to use SVN on
> our very loosely coupled FM docs. No two people were ever working on the
> same parts, and there was little cross-referencing. It was a pain, because
> having nearly zero version control would have been far simpler. Any time
> that something went wrong with SVN (and it did, all too often) we had to
> find the local SVN guru to unscramble it before we could do our work.
>
> I have no idea what the difficulty was with the SVN internals. I've not
> yet had the opportunity to try Git.
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | http://techwhirl.com
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as elisawyer -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
--
Elisa Rood Sawyer
~~~~~^~~~~~
Technical and Creative Writer
"Apparently there is nothing that cannot happen today." Mark Twain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com