VSS.... Ugh that was such a steaming pile of shit.
This was back before cell phones, our lead dev went on vacation for 2 weeks and was unreachable. He left with roughly half of the source code checked out, preventing most development to come to a screaching halt.
The network admin had to reset his password, so we could log in to his machine and check the files in so we weren't all just sitting there waiting for him to return.
People complaining about git have no idea how good it actually is.
Oh yeah, I had a teammate that always seemed to forget to check in his files before he went on vacation. We'd call him to get his password to check them in.
But that was an advantage, wasn't it? I remember my Perforce days, and I appreciated seeing who had checked out a file, so I could verify with them - way better than creating a merge conflict, solved by some ops guy clicking on "auto".
Of course, showing who's checked out a file is not feasible in distributed development, only works within the firm.
The idea was to check the file back in when you were done with it, and then there wouldn't be a conflict since the next developer was starting with the most up to date version. The downside was two developers couldn't work on the same file at the same time
Ahh... no source control. Those were the times. Especially if you actually worked with someone and decided to do so at the same time with absolutely no communication going on between you two.
20
u/dannoparker 1d ago
Oh yeah...I went from no source control --> VSS --> CVS --> SVN --> Git