These are great tips. And so is the other post about Git Koans posted here today. I'm a bit of a git fan and while such tips pique my curiosity and delight the

These are great tips. And so is the other post about Git Koans posted here today. I'm a bit of a git fan and while such tips pique my curiosity and delight the git geek in me, is it actually wise to use these on a day to day basis at your job? Doesn't the argument about 'clever code v/s clear code' apply to highly configurable tools like git? While pairing with others or even using a common dev box, I like to use plain vanilla CLI git without intricate aliases, without intelligent git hooks, or other fancy extensions as far as possible.