Git Magic

This seems to try to get the reader familiar with commands in a verbose sort of way, but IMHO, that's not exactly the best way. See for example the section on branches - it tells you to run certain commands (checkout -b) without telling you what's happening in the background. So while you kind-of get a feel for the command in the context it's being explained, you wouldn't know how to apply it to your context, unless your workflow and…

All these git tutorials are nice, and they might be beneficial for some people. Personally, I find all these supposedly-helpful analogies useless and confusing. If I start to learn git, I would rather someone just tell me three things: 1. Git saves 'entire' snapshots of a directory on each commit. 2. Each commit resides in a graph and has a pointer to its parent 3. The only commit with more than one parent is a merge commit - which carries…

Yet another Git tutorial. I've found that it's impossible to master Git by treating it like a black box- one _must_ understand how it works to truly understand it.

I can't help but think "Does source control matter that much in a startup". I can see why git may be much better than svn for large groups of developers, but is git really that much better for small groups? Are people really spending much time on revision control?