Ok, so I'm trying to get our team moved off a "home grown" version control system that really sucks balls to something a little less buggy (ie. doesn't core dump if you have an apostrophe in a commit message) and a little faster (takes less than 5 minutes to check in a dozen files). And no, I'm not exaggerating. It really is that bad
(
Read more... )
Comments 4
As for Subversion (which I currently actively use and even run a server for), I have to admit that Joel Spolsky is rather persuasive in talking me out of it.
Reply
If you need further convincing, try doing this sometime in a centralized vcs. It gets ugly very quickly, and dvcs handles it remarkably cleanly. In my experience (3+ years using dvcs in professional software development environments, 9+ centralized) distributed is hands-down more powerful, more flexible, more manageable, and all around a better fit for professional software development.
EXCEPT (and this is an important one):
You have to get it. You have to get how distributed works and why. And so does the rest of your team. If the team doesn’t get it, they will screw it up. Code will get lost or mismerged or forgotten or never get pushed to a shared repository, and some recalcitrant teams will even blame the distributed model itself. The problem is that they’re trying to use a screw as if ( ... )
Reply
The real challenge will be to integrate this with the beast that is our current VCS, a thing called "BDM". Here's a description of it I posted on Facebook:
Currently we're using a rather hackish system that's indescribably painful to use. We're doing this because the design team we work with has this particular system baked into all of their workflows. It has all sorts of wonderful quirks ( ... )
Reply
Reply
Leave a comment