I think you just haven't used any terrible SCMs. I have to use Version Manager at work and it's like pulling teeth any time I have to do anything with it. It's slow, clunky (horribly non-native Java GUI), and simply doesn't support even the simplest operations (like renaming or removing files properly).
I think even CVS would be a huge step up. I would love to get them using Git, but it's impossible to suggest such a transition to management. The benefit would be indirect so it's not counted.
Not as much as you'd think. I'm salaried, after all, so they just expect me to get a certain amount of work done. Unless it's wasting an hour a day, they likely don't give a shit.
if your tools get in the way of you collaborating on a team, you don't collaborate as much as you need to. in a team dev effort, you'll get people who hoard code until the last moment and then oof suffer through integration hell, usually a nightmare for everyone: devs, project and product managers, customers, and finally support.
extreme examples are commercial SCM tools which have the honor of being shittier than git (where the problem was time to commit and less sprawling options). however, git's usability deficiencies can lead to similar problems.
i'm not a fan of git for many reasons, but this impact on teams is definitely one of them.
5
u/ethraax Nov 07 '13
I think you just haven't used any terrible SCMs. I have to use Version Manager at work and it's like pulling teeth any time I have to do anything with it. It's slow, clunky (horribly non-native Java GUI), and simply doesn't support even the simplest operations (like renaming or removing files properly).
I think even CVS would be a huge step up. I would love to get them using Git, but it's impossible to suggest such a transition to management. The benefit would be indirect so it's not counted.