Preface

[?]

May 30, 2019, 7:42 PM

QEKU5M3OVXXVOSJUAXAL63VSYARZPXYMZRXPO73BVB574C4JDW7AC

Dependencies

[2] S55XICBM Fix speaker notes
[3] 4AZS4L6B Add chapters
[4] PMBAMPBI Finish the title slide
[5] NYFLNSVV Add some contents
[6] WYULWETJ Reorganize
[7] ARAFRHKU Create the outline of the talk
[8] KPHR32IR Progress
[*] UH3YXOLF Start the slide deck

Change contents

file addition: version-control-timeline.png (----------)

[10.1221]
replacement in sections/0-welcome.md at line 27

[3.1515]→[2.405:456](∅→∅)

And the office cafeteria serves stroopwafels ONLY.

[3.1515]

[2.456]

And when it's lunch time, the office cafeteria serves stroopwafels ONLY.
replacement in sections/0-welcome.md at line 31

[2.600]→[2.600:657](∅→∅)

I didn't say WHEN you get bored, I said IF you get bored!

[2.600]

I didn't say WHEN you get bored, mind you, I said IF you get bored!
There's a difference!
replacement in sections/1-preface.md at line 3

[3.1990]→[3.1990:2017](∅→∅)

# Teaching A Course On Git

[3.1990]

[3.2017]

# Teaching a course on Git
replacement in sections/1-preface.md at line 14

[3.2468]→[3.2468:2611](∅→∅)

It's a one-day course where we teach the students how to use Git as a developer (none of that GUI stuff of course; command-line For The Win!).

[3.2468]

[3.2611]

It's a one-day course where I teach the students how to use Git as a developer (none of that GUI stuff of course; command-line For The Win!).
replacement in sections/1-preface.md at line 16

[3.2787]→[3.2787:2933](∅→∅)

Now the other day a student came to me after attending the course and said: "Git is great and all that, but what is gonna be the next big thing?"

[3.2787]

[3.2933]

---



[http://blog.plasticscm.com/2010/11/version-control-timeline.html](http://blog.plasticscm.com/2010/11/version-control-timeline.html) 

note:
This is actually one of the course slides.
And it shows which version control systems have emerged in the past and when they became available.
It tries to put the publication date of each version control system in perspective by comparing them to the most modern phone known at that time.

So, Subversion relates to the Nokia 3210, for example. (*point*)
And CVS relates to the thing with the power plug.

Now, when I talk about this slide during the Git course, I tend to focus on the events of the year 2005.
Because to me, 2005 REALLY stands out in version control history.
I mean, FIVE new version control systems were published in that year.
In a single year.

To put this number in context, before 2005, it had taken NINE years for five version control systems to emerge.
Starting with VSS in 1994, and ending with BitKeeper in 2003.
And in 2005, it all happened within a few months.

So, who knows why it happened like this?

---

note:
The answer is BitKeeper!

---



[http://blog.plasticscm.com/2010/11/version-control-timeline.html](http://blog.plasticscm.com/2010/11/version-control-timeline.html) 

note:
Now just because I thought the year 2005 really stood out in this graphic, doesn't necessarily mean it was like that for everyone.
In fact, at the end of the course day a student came to me with a question.
And his question proved that he had noticed an entirely different thing than I had noticed.
Moreover, his 'discovery' - if you will - proved to be a LOT more interesting than mine.

He came over to me and said: "Git is great and all that, but what is gonna be the next big thing?"
So I told him I was quite sure distributed version control systems like Git and Mercurial would be around for a while longer.
But to be honest, I didn't really know the answer.
So it was a great question, actually.
replacement in sections/1-preface.md at line 64

[3.2934]→[3.2934:3193](∅→∅)

Which was a great question, because I couldn't really answer it.
I was quite sure distributed version control systems like Git and Mercurial would be around for a while longer, so that's what I told him.
And he replied: "Surely Git won't be around forever?!"

[3.2934]

[3.3193]

And he was right in asking this question, of course.
Because if you look at the chart and you look beyond what you've already seen (the year 2005), then it becomes painfully obvious
In version control land, nothing seems to have happened after 2006.
This is one of those things that, once you see it, you can't UNSEE it.

---

note:
replacement in sections/1-preface.md at line 95

[3.2037328]→[3.7966707:7966839](∅→∅)

So, whenever I hear somebody say that [insert-product-name-here] "will probably be around forever", it immediately reminds me of...

[3.2037328]

[3.973996]

Now, whenever I hear somebody say that [insert-product-name-here] "will probably be around forever", it immediately reminds me of...
replacement in sections/1-preface.md at line 128

[3.2038144]→[3.7967018:7967124](∅→∅)

Now if "Change is the only constant" is valid in our industry, then so is "What goes up, must come down".

[3.2038144]

[3.2038144]

Now if the idea of "Change is the only constant" is valid in our industry, then so is the idea of "What goes up, must come down".
replacement in sections/2-git.md at line 3

[3.7969464]→[3.3881:3906](∅→∅)

# Why Is Git So Popular?

[3.7969464]

[3.7969465]

# Why has Git become so popular?
edit in sections/2-git.md at line 9

[3.7969613]

[2.659]

Now if we want to be able to predict 'the next big thing' in version control, surely some information on the 'current big thing' is very relevant to our quest.
Moreover, it could be useful to understand how 'the current big thing' became 'the big thing' in the first place.

---



[https://blog.gitprime.com/git-didnt-beat-svn-github-did/](https://blog.gitprime.com/git-didnt-beat-svn-github-did/) 
edit in sections/2-git.md at line 19

[2.660]

[2.660]

note:
Here is some information on how 'the current big thing' - which is Git - became 'the big thing'.
edit in sections/2-git.md at line 65

[3.7970915]→[3.2039979:2039980](∅→∅),[3.2039979]→[3.2039979:2039980](∅→∅),[3.2039980]→[2.751:755](∅→∅)

---
edit in sections/2-git.md at line 66

[2.756]→[3.2039980:2040273](∅→∅),[3.2039980]→[3.2039980:2040273](∅→∅)



[https://blog.gitprime.com/git-didnt-beat-svn-github-did/](https://blog.gitprime.com/git-didnt-beat-svn-github-did/)