Quite verbose and I feel like it doesn’t actually explain things that will. E.g. jumping straight into branches is a weird order.
I can’t remember where I read it but the thing that made me understand Git was some tutorial that started out with “what would you do without git? You might copy & paste your whole project and add V2 on the end, then V3 etc. Those are commits. Now you want to keep track of things so you record parents etc…”
Semantically git is extremely simple so I don’t think it takes long to explain it properly. The really tricky bit is the CLI, but my very strong recommendation is to not use the CLI until you have some experience of the semantics via a good GUI (e.g. Git Extensions) because you’ll need a good mental model of what you are doing if you can’t actually see it.
Quite verbose and I feel like it doesn’t actually explain things that will. E.g. jumping straight into branches is a weird order.
I can’t remember where I read it but the thing that made me understand Git was some tutorial that started out with “what would you do without git? You might copy & paste your whole project and add V2 on the end, then V3 etc. Those are commits. Now you want to keep track of things so you record parents etc…”
Semantically git is extremely simple so I don’t think it takes long to explain it properly. The really tricky bit is the CLI, but my very strong recommendation is to not use the CLI until you have some experience of the semantics via a good GUI (e.g. Git Extensions) because you’ll need a good mental model of what you are doing if you can’t actually see it.