>That sucks for beginners, but once you get over the hump, git is like a chef's knife
When do you get over the hump? I've been using git for nearly a decade, I understand the internals of its data structures, I can talk about the difference between a rebase and a merge, and I still need to reference a cheat sheet for anything more complex than creating a branch, pulling from head, and committing.
What really helped me was to create aliases and short scripts for the variety of commands that I used. For example, I created a small script called `git-back` that is `git reset --soft HEAD^1`. The `git-back` takes a parameter for how many commits back you want to go.
Not sure if this is what everyone wants, but adding a wrapper language around the commands was really powerful for me. Everything could be tab completed, used names and terms that I could remember, and at times the new commands became so baked into my mind I forget at times they are not part of core git.
When do you get over the hump? I've been using git for nearly a decade, I understand the internals of its data structures, I can talk about the difference between a rebase and a merge, and I still need to reference a cheat sheet for anything more complex than creating a branch, pulling from head, and committing.