Ask HN: How can I get my team to adopt SCM?
I don't work among programmers. Everyone on my team has a statistics degree, and most only had one or two CS classes in their undergraduate (for many, this was 15-25 years ago) and do not follow any of the practices or paradigms of software engineering rigorously. I've recently been trying to get subversion (one other guy knows it) or git (I know it, it seems nicer for programming without internet access), but my coworkers and boss cannot see the need. Most programs are only written by one person, but viewed by more than a dozen others, who submit revisions and requests via email, sometimes merging their own code in by hand. What perks of SCM can I cite that my team would find beneficial, other than making merges easier (a rare task we need to do)?
4 comments
[ 980 ms ] story [ 668 ms ] threadThe added team working enhancements are always secondary to version control and if someone can't see the benefit of this it is going to be hard to argue.