[grannyg00se]

A lot of these Git tutorials seem to walk you through a series of commands as if knowing the commands is knowing Git.

I think they should focus on scenarios instead. Short stories like: "Bob's code is working well but he wants to try something that might be completely misguided. He knows better than to mess with his working code....." Then at the end of the story a command is introduced. Also, some kind of indication of what Git is actually doing when you issue that command. When you tell Git to branch, what actually happens to the file system? When you say git status, what is it actually looking at?

And please, don't start a tutorial on Git without introducing the three area paradigm (working, staging/index, commit)

Here's a talk by Scott Chacon of GitHub. http://www.youtube.com/watch?v=ZDR433b0HJY

It's over an hour long and very detailed.