The anatomy of distributed development - a full catalog of do's and don'ts
As version control developers we meet teams transitioning to different development patterns on a daily basis.
In the enterprise world many are scared to jump into distributed development since they think it will mean a total loss of control. They also tend to think "distributed doesn't fit here".
Others think they're already distributed because they use some sort of connection to a central server :-P
We posted about DVCS myths before but this time we're going to share a full list of typical cases trying to figure out how different types of teams look like... while having some fun.
We will be covering all these topics on our upcoming webinar on July 10th
We'll also check which "myths" are real or ... busted! :D
The DVCS crowd
There is really not much to say about this group other than they're the ones really getting the most about distributed version control. Early adopters, enthusiasts... contributors to open source projects, git and mercurial users most of them, they truly understand what pushing and pulling is all about, merging and all that.
The “distributed for the enterprise”
This is the group where we really focus with our product. The challenge is to get the best of the DVCS world and put it together with the needs of the teams developing commercial and corporate software, which don't always match the ones in the pure DVCS world.
Here comes the fun part. These are the folks who *believe* they're already fully distributed and cool and all that... but they don't realize reality is slightly different :D
They don't embrace distributed development because they still don't need it or maybe because they even care!