>>The good and bad of git is, that there is no really right or wrong.
>
>Totally agree.
>
>I had a hard time initially getting comfortable with Git. There are many different ways to use it obviously. If you use for just local 'source control' backups, then using `git commit -a` is probably all you need. And that's likely how most will start. But as you use it more you start to realize the power of branching, rolling back and switching between branches. Then there's all the intracacies of sharing via distributed repos like GitHub. etc.
>
>I think it's a process. For me I started using it for simple stuff first (mostly for my own repos) and slowly over time I started using more and more of it. It's now been close to 10 years though and even now there are still tons of things that are a mystery to me. But at the same time I have what I need to get work done - by myself or in a team environment.
>
>Just because a tool is very complex doesn't mean you a) have to know it all at once, or b) use a lot of it to get value out of it.
>
>Git is arcane and frankly was never the best choice for source control, but it's pretty much what's taken over and I can't see it changing to something new anytime new. It works and it's proven itself to work at very large scale as some of the world's largest projects (including Windows which I believe may be **the** largest) are using Git.
>
>Today I can't imagine **not** having solid source control to help me while experimenting with code, or simply as an error recovery mechanism, let alone for sharing code. I pretty much share everything these days which is so much easier with places like GitHub or BitBucket. Think about how much value those Free services provide - it's immense.

Full ack
It's a bucket of wonders - and I will learn a new one from time to time. Last one to me was git worktree (*.*)

Have I nice day. I'm closing down.