GIT is a great tool… in the same way that an advanced CNC milling machine is a great tool. If you’re working in a very specialized environment, with highly skilled craftspeople that are well-trained and understand how to properly use – and what the dangers are – of such a tool, then it is the appropriate tool for that environment. That environment is most likely producing specialized items; prototypes, one-off’s, uniquely difficult items to fabricate, or have other special needs (the machine shop at NASA’s Jet Propulsion Laboratory comes to mind). I’ll admit, a CNC milling machine is pretty cool… I’ve used (and accidently abused) them. But when my task was to quickly drill a hole, I didn’t want to waste time trying to set up that complex machine when a simple drill press – or even hand drill – would do the job more quickly and safely. In fact, if you need to quickly and safely attach part A to part B, you don’t want a CNC milling machine, you want a power screwdriver; maybe one with torque settings, speed control, and a few other simple, self-obvious features. It’s going to let you focus on your job of attaching the parts together and moving on to the next task. Something like Subversion or the myriad of other source control systems that aren’t so cool but do their job of managing source, and allow me, as a developer, to intuitively check out, update, merge, diff, and check in source code. So if you’re developing something specialized, like the Linux kernel, or have a relatively small team of highly distributed people whom you can afford to train (and pay accordingly), then by all means you should consider GIT. That is the environment and skill level the tool was developed for. But if your focus on writing software, with teams of developers at a various skill levels, and you want them to focus their time and effort on developing the software business solutions that make your company money, then GIT is most likely not the appropriate solution, no matter how “cool” folks say it is. BTW, we are a small, start-up, who hastily chose GIT because “everyone is going to it”. After a year, no one in the organization is comfortable with it, most of the developers don’t trust it because we have all managed to destroy work by doing “what seemed intuitive”, and it's a decision we all regret.