“As much as I’d love our code to be fully compliant with the great programming practices of this world, I’d rather have it working — if possible before the heat death of the Universe.”
To me it comes down to the amount of black magic done by GUIs.
I prefer to use the CLI for write operations because of simplicity — I can easily control what I do, while most GUIs do a lot more than just commit -m or push.
I prefer to use GUIs for read operations because of complexity — they combine commands in a powerful way and get the most out of Git.
To truly understand what Git is or what Git does, though, I’ll never not recommend this amazing guide.
Totally agree. I think GUIs do a very good job in visualizing the status of the repo and history. Far better CLI can.
I am going to take a look at that guide you recommended. I like the idea of explaining Git concepts rather than commands. I think most Git tutorials geared towards beginners are too focused on HOW to do stuff rather than WHY.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To me it comes down to the amount of black magic done by GUIs.
I prefer to use the CLI for write operations because of simplicity — I can easily control what I do, while most GUIs do a lot more than just
commit -morpush.I prefer to use GUIs for read operations because of complexity — they combine commands in a powerful way and get the most out of Git.
To truly understand what Git is or what Git does, though, I’ll never not recommend this amazing guide.
Totally agree. I think GUIs do a very good job in visualizing the status of the repo and history. Far better CLI can.
I am going to take a look at that guide you recommended. I like the idea of explaining Git concepts rather than commands. I think most Git tutorials geared towards beginners are too focused on HOW to do stuff rather than WHY.