7
GiddyNaya
362d

I just scroll past this question asking how to get good at Git commands (https://devrant.com/rants/9997784/...). Figured I'd share my thoughts as a separate rant cause it's a topic I've tinkered with a bit.

So, My initial engagement with git-related queries on StackOverflow dates back to around 2021.. Surprisingly, one of my short and straight-to-the-point replies got a hand full of attention. You can check it here: https://stackoverflow.com/a/...

Now, about mastering Git commands – from my own trial and error:

1). Instead of trying to cram everything into your big brain, scribble down notes. Trust me, it’s more practical. I kept a cheat sheet of sorts as notes on my PC, noting down the commands I used day in, day out. Super handy beyond just work stuff.

2). You gotta get what each command does, but you don't need to nail it all at once. Spend a day diving into the basic commands. Leave the trickier ones for later; they start making sense as you get more into it.

3). I had this aha moment when dealing with a merge mess using a GUI tool. Switched to the command line, and bam! It made way more sense. The command line's like a secret passage to really understanding Git.

So, if you're wondering how to tackle Git commands, my take is: *notes, *baby steps, and *lean into that command line magic. Mix them up your way and see what sticks for you!

Comments
  • 1
    I agree - the CLI forces you to actually know what you are doing. If you use a GUI and don’t know how the underlying system works, you are just using a more abstracted software, farther away from being capable to speak easily to git. Nothing should be magical IMO.

    However, as someone who learns visually and tactically, there’s plenty of free online courses that can help you visually understand the commands and how the version history tree(s) are constructed using commands.
Add Comment