Sometimes I think back to that time that I explained git to a bunch of colleagues the way I would have wanted it explained to me.
It would become clear that nobody there wanted git explained to them that way.
Sometimes I think back to that time that I explained git to a bunch of colleagues the way I would have wanted it explained to me.
It would become clear that nobody there wanted git explained to them that way.
@clacke please tell. I’m holding a one day git course next week and it would be great to know what not to say. 😁
@jonatanskogsfors I started with a brief overview of the history of version control, like RCS, CSV, Subversion, bitkeeper, what changes they made to the abstract data model and what features that allowed, and then I showed the anatomy of the git data model, abstract and concrete, interactively on the command line, inspecting the blob, the tree and the commit.
So that people really understand where everything is coming from when you do a git commit or git checkout.
People were kind. Comments like "... interesting, but maybe a bit advanced".
I think what they meant was "you took an hour of my time and I still don't know why there's git fetch and why github says my master is 50 commits behind".
@clacke I like you version and have had very similar thoughts. I will however save the data model to a bit later when some key actions have been presented. I finally got my head around the (very elegant) data model after years of giting and so much clicked for me. My key message that I want to teach is the importance of internalizing the model before you do anything more advanced than a commit.
@clacke and also that you will never stop screwing up. Just get to know some strategies for undoing. When in doubt, SO and https://ohshitgit.com.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.