[rajat]

I sympathize. What is really necessary are not tutorials on how to use Git--it isn't that hard, after all, for most of us--but more of a description of actual workflow. Not HOW you issue Git commands; but how to use Git.

It would be interesting to read articles about how a single programmer uses Git, how a small programming team, how a distributed team uses Git. Similar articles about how a team producing art, or text (not programmers) use Git.

There's plenty of Git command tutorials already; let's hear about how you actually use Git.

[kalid]

I completely agree. If it helps, I wrote up some visual tutorials about version control in general that many have found helpful:

http://betterexplained.com/articles/intro-to-distributed-ver...

The idea is to build a mental model about what is possible vs. memorizing a bunch of specific commands. Once I wrapped my head around the concepts, the commands fell into place.

[gizzlon]

Looks good!

On my screen the text is light gray on white. Is that intentional?

[kalid]

Whoops! Thanks for the comment, the text should be a readable black on white (like this: https://skitch.com/kalidazad/er7an/intro-to-distributed-vers...).

Which browser were you using? (I just tried FF, Chrome, Safari) Thanks!

[gizzlon]

https://skitch.com/gizzlon/efrsh/screen

[kalid]

Thanks, really appreciate it!

[dsirijus]

Agreed. And not only for Git. For basically anything else in programming land you get to have either hands on quick guides or spec listing. There's serious shortage of good, moderately abstract, short overviews of what something actually does and how it does it.

Take Vim for instance. When I first got to it, I found only resources that are paraphrased with "this command does that. that command does that... nth command does that". Now, if only someone described buffers, tabs and windows to me (like in an article that was recently linked to here on HN), or told me that commands can be described as acronyms of verbs and nouns etc. I'd be much more proficient with Vim now.

For Node.js, I found some talks/presentations from its creator that really hit this spot.

I still haven't found anything like that for Git.

[vrishabh]

> For Node.js, I found some talks/presentations from its creator that really hit this spot.

Mind sharing the specific ones which worked for you?

> I still haven't found anything like that for Git.

I shared a nice conceptual tutorial about git in a reply in another comment of the same thread. Here it is, http://news.ycombinator.com/item?id=4200426

[dsirijus]

Sure. Sorry for not linking to any in the first place.

Here it is http://youtu.be/M-sc73Y-zQA. He got cocky later on, so I don't like very much his presentations of a later date. In this one, he's pretty nervous on occasions. It's cute. :)

I just glanced at the git tutorial provided - it seems it is up my alley. Will check it out later on.

[v33ra]

Sometime back, I wrote about my initial Git workflow: http://veerasundar.com/blog/2011/06/git-tutorial-my-git-work...

[RollAHardSix]

Correction, what we need is both. Tutorials and a description of the workflow. The articles are all nice touches as-well. Knowing how my team could be more organized helps me want to try it out.

And just in-case I came across as an asshole, I liked your post and thought it was great :)