3 ms·
> * (locally I've been smashed into teams still on svn ... on new projects)* Completely off topic, but: is this necessarily bad? Does the world stop when there
by skrebbel 15y ago
> * (locally I've been smashed into teams still on svn ... on new projects)*
Completely off topic, but: is this necessarily bad? Does the world stop when there's a centralized source control server?
I'm in an environment too where people are sometimes reluctant to move to newer, better software (svn is an example, our bug tracker sucks too), simply because of the learning curve / overhead involved. I started out by being annoyed with this, until I realized that at the same time using modern SW development practices is really what matters (e.g. a lot of TDD, BDD, MDSD here). I can survive svn, but I can't survive the waterfall model.
- r4vik 15y agoI can't talk for TDD, BDD, MDSD. But after working with git/hg on all my projects for half a year, I'd flat out refuse to work on anything that used SVN now.
- skrebbel 15y agoGenuine interest: why? I felt the same, until I realized that I also want continuous integration, preferably as continuous as possible. This means that if my coworker works on a feature that somehow affects what I'm working on, I want to find out now, not in a week after he merges his feature branch. If there's a single central repository anyway (continuous integration, remember), plus you want people to share with master/trunk/whatever after being under water for at most 2 days, the workflow when using git/hg becomes awfully much like the workflow that SVN enforces on you. When I realized that, I stopped investing time in converting my colleagues to git. I use git-svn myself so that I can stash, move files without `svn move`, do local commits, etc, and everybody is happy. But I may be missing a great argument.
- r4vik 15y agoCI is a good argument for centralised source control, and like you say it is possible to get 90% of the benefits just using git-svn (I have done in the past). The real power for me is the branching, especially shared branching. My workflow is like this, each dev has their own github repo which is up to date with whatever is in their local repo. So even if someone is working on esoteric weird crap, I can see it (ircbot telling you about commits) and I can pull it. For CI we have a server that is also running a git repo of it's own. Anyone can push branches to it and they'll get put through CI. So I can now take my branch, pull 3 or 4 peoples feature branches merge them locally then push to CI repo to see if anything is broken. If it is, I can fix some of it and push it back to whoever needs to know if there is something I don't understand. It's a joy.
- Swizec 15y agoI find the use of SVN to be a good predictor for a place using the waterfall model and calling it "agile", not using TDD and so on. It's my "one wrong candy" clause if you will. (can't find the article right now, but some bands make one insane request for their backstage that can be instantly checked, when it isn't perfect, they know to check through the whole list of the stage setup and so on, otherwise people literally die when something breaks)
- anthuswilliams 15y agoWow. My "no black M&Ms" rule is a lot less discriminating than yours (btw, the band you're thinking of was van Halen). I don't care if clients use SVN, or CVS, or whatever they want. I just want the answer to the question "What do you use for source control?" to be something other than "Source control?"
- Swizec 15y agoI guess times change? Five years ago, that was my black M&M too.