"On top of that, it’s actually not that hard to understand, and once you do, a whole new world will open up."
While I agree with the author I must point out that it will take some effort for average users to understand what goes on behind the scenes. Especially if they have been using CVS/SVN for long.
I came to git from SVN. It took me a good hour of working through the key diagrams/explanations using a pencil and paper to figure out the git model. And once I did git became a pleasure to work with.
I find that some of my fellow developers are averse to making this initial investment of time and brain cycles to understand the theory of git. Some of them feel that a version control system isn't worth spending time on. Some of this reluctance has to do with how one is introduced to source control. Many learn about version control from "senior developers". More often than not CVS/SVN is explained away as "tracking diffs". Naturally when faced with something like git they ignore it or balk at the idea.
While I agree with the author I must point out that it will take some effort for average users to understand what goes on behind the scenes. Especially if they have been using CVS/SVN for long.
I came to git from SVN. It took me a good hour of working through the key diagrams/explanations using a pencil and paper to figure out the git model. And once I did git became a pleasure to work with.
I find that some of my fellow developers are averse to making this initial investment of time and brain cycles to understand the theory of git. Some of them feel that a version control system isn't worth spending time on. Some of this reluctance has to do with how one is introduced to source control. Many learn about version control from "senior developers". More often than not CVS/SVN is explained away as "tracking diffs". Naturally when faced with something like git they ignore it or balk at the idea.