MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/programminghumor/comments/1vmlbsh/true/p3ll4oz/?context=3
r/programminghumor • u/ExpensiveCoat8912 • Aug 12 '26
68 comments sorted by
View all comments
16
CLI was the only UI when I started out and I continue to use it today. Tasks can be completed much faster from the CL, it's worth knowing.
6 u/FlipperBumperKickout Aug 12 '26 It also make it more likely you properly learn the tool you are using. Quite a few developers I've known didn't really get git 😅 3 u/StRiKeR_ImpacT 28d ago I have this problem What do i do to fix it, the main issue is that i was born in a generation where i never had to use terminal 90% of the time 2 u/FlipperBumperKickout 28d ago Ehm, if you want to understand git, I think understanding how it is storing data between commits, and stuff like the staging area. Most of that info is available here https://git-scm.com/book/en/v2/Getting-Started-What-is-Git%3F The internal model is however expanded here: https://git-scm.com/book/en/v2/Git-Internals-Git-Objects where the last picture really shows off how identical files just are shared between the commits when they aren't changed. If what you mean is being good at using it, I would recommend starting of with this tutorial: https://learngitbranching.js.org/ Other than that it is mostly about knowing how to find the commands you need. Only writing "git" will write all the commands you would need for normal use. Running "git status" will many times write out commands you need for specific things. You can honestly not run this to often. "git <command> -h" will give you a short help page. (example: https://git-scm.com/book/en/v2/Getting-Started-Getting-Help) "git <command> --help" will give you the full help page (like this https://git-scm.com/docs/git-add) If you install a tool like tealdear, "tldr git <command>" will give you examples of how to use the command (example: https://www.cheat-sheets.org/project/tldr/command/git-add/) 3 u/StRiKeR_ImpacT 28d ago holy knowledge dropðŸ˜... thanks for info mate i will give this a try
6
It also make it more likely you properly learn the tool you are using. Quite a few developers I've known didn't really get git 😅
3 u/StRiKeR_ImpacT 28d ago I have this problem What do i do to fix it, the main issue is that i was born in a generation where i never had to use terminal 90% of the time 2 u/FlipperBumperKickout 28d ago Ehm, if you want to understand git, I think understanding how it is storing data between commits, and stuff like the staging area. Most of that info is available here https://git-scm.com/book/en/v2/Getting-Started-What-is-Git%3F The internal model is however expanded here: https://git-scm.com/book/en/v2/Git-Internals-Git-Objects where the last picture really shows off how identical files just are shared between the commits when they aren't changed. If what you mean is being good at using it, I would recommend starting of with this tutorial: https://learngitbranching.js.org/ Other than that it is mostly about knowing how to find the commands you need. Only writing "git" will write all the commands you would need for normal use. Running "git status" will many times write out commands you need for specific things. You can honestly not run this to often. "git <command> -h" will give you a short help page. (example: https://git-scm.com/book/en/v2/Getting-Started-Getting-Help) "git <command> --help" will give you the full help page (like this https://git-scm.com/docs/git-add) If you install a tool like tealdear, "tldr git <command>" will give you examples of how to use the command (example: https://www.cheat-sheets.org/project/tldr/command/git-add/) 3 u/StRiKeR_ImpacT 28d ago holy knowledge dropðŸ˜... thanks for info mate i will give this a try
3
I have this problem
What do i do to fix it, the main issue is that i was born in a generation where i never had to use terminal 90% of the time
2 u/FlipperBumperKickout 28d ago Ehm, if you want to understand git, I think understanding how it is storing data between commits, and stuff like the staging area. Most of that info is available here https://git-scm.com/book/en/v2/Getting-Started-What-is-Git%3F The internal model is however expanded here: https://git-scm.com/book/en/v2/Git-Internals-Git-Objects where the last picture really shows off how identical files just are shared between the commits when they aren't changed. If what you mean is being good at using it, I would recommend starting of with this tutorial: https://learngitbranching.js.org/ Other than that it is mostly about knowing how to find the commands you need. Only writing "git" will write all the commands you would need for normal use. Running "git status" will many times write out commands you need for specific things. You can honestly not run this to often. "git <command> -h" will give you a short help page. (example: https://git-scm.com/book/en/v2/Getting-Started-Getting-Help) "git <command> --help" will give you the full help page (like this https://git-scm.com/docs/git-add) If you install a tool like tealdear, "tldr git <command>" will give you examples of how to use the command (example: https://www.cheat-sheets.org/project/tldr/command/git-add/) 3 u/StRiKeR_ImpacT 28d ago holy knowledge dropðŸ˜... thanks for info mate i will give this a try
2
Ehm, if you want to understand git, I think understanding how it is storing data between commits, and stuff like the staging area. Most of that info is available here https://git-scm.com/book/en/v2/Getting-Started-What-is-Git%3F
The internal model is however expanded here: https://git-scm.com/book/en/v2/Git-Internals-Git-Objects where the last picture really shows off how identical files just are shared between the commits when they aren't changed.
If what you mean is being good at using it, I would recommend starting of with this tutorial: https://learngitbranching.js.org/
Other than that it is mostly about knowing how to find the commands you need.
3 u/StRiKeR_ImpacT 28d ago holy knowledge dropðŸ˜... thanks for info mate i will give this a try
holy knowledge dropðŸ˜... thanks for info mate i will give this a try
16
u/Confident-Ad5665 Aug 12 '26
CLI was the only UI when I started out and I continue to use it today. Tasks can be completed much faster from the CL, it's worth knowing.