Today I am teaching a few people #git
Guess what? I am not starting with git itself, but with "version control" as a concept first. These people are apprentices at my employer and I think teaching them about why we want to do VC is more beneficial than just teaching them git right away - because one first needs to learn why a tool is helpful and _then_ the tool itself, not the other way round.
What'd you think?
@musicmatze COPY_OF_code.zip
@musicmatze This is spot on, IMO, particularly with tools that can be confusing/frustrating/challenging, having a firm grasp as to why they are useful makes a *huge* difference in the willingness to push through initial learning hurdles.
@musicmatze that's a really good approach. You're doing important work there, thank you!
If anyone of the folks you're teaching need a hand in the future, please feel free to point them my way if you're busy. I'll help them out.
So what I've worked out in preparation now:
* First of all what _is_ VC
* Why would anyone need VC (basic ideas why we would keep old copies of things)
* Local VC (think v1.zip, v2.zip) + discussion (semantics, problems, ...)
* Central VC (think SVN) + discussion
* Decentral VC (w/o mentioning the implementation)
* Concepts of decentral VC - "servers" (plural), "working copy", later "branches" (without mentioning the term)
* Workflows (branching model, CI,...)
And next week the implementation: git.