If you try to learn git one command at a time on the fly, git is HARD. If you take the time to understand its internal data structure it’s much, much easier to learn. Unfortunalely most people try to do the former because it works well (or better) for most tasks.
Thanks. I guess it’s the perpetual problem of learning something new. Instead of starting at the beginning, we trick ourselves into thinking that we can skip the fundamentals. Then we have difficulty and think that the problem is one of complexity or just over our heads instead of our approach.
In fairness, sometimes it is useful to get hands on experience with a system before you dig into its fundamentals so that you have a reference point that helps you absorb the information.
https://learngitbranching.js.org
Is a very accessible browser game that I found useful on my Git journey to start to grasp the underlying structures and operations such as rebase.
I am in a perpetual wonderland of git confusion, but this was a good read. And maybe I now have a pathway to enlightenment.
If you try to learn git one command at a time on the fly, git is HARD. If you take the time to understand its internal data structure it’s much, much easier to learn. Unfortunalely most people try to do the former because it works well (or better) for most tasks.
I can’t recommand enough the git parable.
Thanks. I guess it’s the perpetual problem of learning something new. Instead of starting at the beginning, we trick ourselves into thinking that we can skip the fundamentals. Then we have difficulty and think that the problem is one of complexity or just over our heads instead of our approach.
In fairness, sometimes it is useful to get hands on experience with a system before you dig into its fundamentals so that you have a reference point that helps you absorb the information.
https://learngitbranching.js.org Is a very accessible browser game that I found useful on my Git journey to start to grasp the underlying structures and operations such as rebase.