Your comment comes off as arrogant and patronizing. I don't know if that's you you meant it, but I'm going to assume so because it's fitting with your other com

Your comment comes off as arrogant and patronizing. I don't know if that's you you meant it, but I'm going to assume so because it's fitting with your other comments. > My brother in Christ disingenuous start, this will be interesting... > why should I put in the time and effort to learn an auxiliary tool to my job? if you think git (or version control) is auxiliary tool then you have not worked on real software. I'm not saying this is you, but IF it's you (or anyone else reading): Writing side scripts and minor modifications on an existing project is not building real software, it's hobby coding, which is fine but you don't get to act like a software engineer. You're as much an engineer as someone cooking a random meal once a week is a chef. > I learned Z80 assembly when I was 12 years old. Prolog when I was 15. When git came ... it was an absolute impenetrable brick wall and let me emphasize Did you consider maybe that your "learning" of z80 asm or prolog was not complete? or possibly faux, false, fake, or gasp you're might not be as smart as you think? Or that when you were a kid you had way more time on your hands than now? The possibilities are infinite for an explanation (that is if what you're saying is true). "OMG Git is hard" is not one of the first 100 reasons that come to mind. > It was not until Charles Duan's git tutorial that I felt I am comfortable with it That's a good tutorial, but you never get comfortable with Git (or any other technical subject matter imho) until you work with it, and it will take practice and -sorry to say- humbleness in that you (or anyone else) can have hard time understanding something that many others find simple. It doesn't automatically mean it's a hard subject because you find it hard. Git is _not_ anymore hard that any other abstraction. You work hard you learn, you don't you won't.