4 ms·
Here is another approach: Back in the bad old days before git I was in a 20-30 person company that used Microsoft's SourceSafe. For anyone unfamiliar it had a
by OscarTheGrinch 6y ago
Here is another approach:
Back in the bad old days before git I was in a 20-30 person company that used Microsoft's SourceSafe. For anyone unfamiliar it had a basic library type structure where only one person could get out (lock) a file at a time.
Now the obvious downside is that when someone goes on holiday or simply forgets those locked files can become blockers. The solution to that is to have an admin unlock the files, which was pretty easy, then a merge, which is basically what happens by default with git.
The upsides of the library approach were a) that I could scan the top directory, and quickly drill down to see who was working on what. b) I feel that walking over to someone's desk and asking if they were still working on a file produced some great back and forth, that was where the magic of collaboration actually happened.
- roland35 6y agoCentralized still makes sense for some things that should not be collaborated on simultaneously! I have used git when working with electronics and part libraries, but there were occasionally merge conflicts with the files when someone would forget to merge their work in. I wish we would have used SVN for those things!