My experience is that the power of any technology unfolds gradually - with git it's like okay let's master the commands for a single repository on a single serv

My experience is that the power of any technology unfolds gradually - with git it's like okay let's master the commands for a single repository on a single server for a single user up to a certain level of adequacy. Then (depending on need), let's add multiple repositories on the same single server for the same single user. Then add multiple servers (including a git remote server). Then add multiple users ... etc ... of course the magic of git is you can unfold those needs in any sequence. Often when I find I do not understand something (that I thought I understood), I go back in scope to an earlier unfolding, eliminating other factors. I'm sure git can be improved, but I think the biggest improvement comes from the user being improved with their understanding of the scope of capabilities. I have yet to see a good tutorial on this (among the plethora of git tutorials out there). This reminds me of the (excellent) video where the "Harvard Professor Explains Algorithms in 5 Levels of Difficulty" [1] [1] https://www.youtube.com/watch?v=fkIvmfqX-t0 https://www.youtube.com/watch?v=fkIvmfqX-t0 I would love to see a Channel where that is the entire theme - explaining everything in 5 levels of difficulty. All this being said, at each of the "5 levels of difficulty" of git, are there improvements to be made. I'm sure there are. It would be good to focus the answer on each of those levels.