It's true only from your world view. You should have titled the post "Git is hard for me" but it would have attracted less eyeballs.
I'm a daily user of Git interacting with thousands of developers committing against the same repo. Here's my sole alias
l = log --graph --pretty=format:'%C(yellow)%h%C(cyan)%d%Creset %s %C(white)- %an, %ar%Creset'
I'm not saying that "I'm so smart I don't need aliases" or that "you're so dumb that you need them" which is how my post is likely to be interpreted.
I'm saying that your past usage and experience may differ so much that it's hard to change the patterns set in your brain. I work with folks who have used Perforce for a decade and struggle with Git. They're super smart but Git is very different and therefore difficult for them at least at the start.
Generally speaking I would recommend avoiding sugar. I sometimes interview folks with so many Bash aliases on their own workstation they can barely navigate using vanilla Bash.
I understand Perforce users you are talking about, but their problems are temporary and that's OK - almost anyone changing main language from Java to Haskell need some time to start feeling comfortable and get productivity to his usual level.
But about Bash aliases - is there any real need to use vanilla Bash (or sh, or ksh, or csh) when he has his settings/aliases file with him?
Comments
This video is funny because it's true.
Git is practically unusable for all but the simplest things without a good set of aliases or wrapper scripts.
It's true only from your world view. You should have titled the post "Git is hard for me" but it would have attracted less eyeballs.
I'm a daily user of Git interacting with thousands of developers committing against the same repo. Here's my sole alias
l = log --graph --pretty=format:'%C(yellow)%h%C(cyan)%d%Creset %s %C(white)- %an, %ar%Creset'
I'm not saying that "I'm so smart I don't need aliases" or that "you're so dumb that you need them" which is how my post is likely to be interpreted.
I'm saying that your past usage and experience may differ so much that it's hard to change the patterns set in your brain. I work with folks who have used Perforce for a decade and struggle with Git. They're super smart but Git is very different and therefore difficult for them at least at the start.
Generally speaking I would recommend avoiding sugar. I sometimes interview folks with so many Bash aliases on their own workstation they can barely navigate using vanilla Bash.
I understand Perforce users you are talking about, but their problems are temporary and that's OK - almost anyone changing main language from Java to Haskell need some time to start feeling comfortable and get productivity to his usual level.
But about Bash aliases - is there any real need to use vanilla Bash (or sh, or ksh, or csh) when he has his settings/aliases file with him?