this post was submitted on 12 Apr 2024
56 points (91.2% liked)
Programming
17538 readers
209 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.