Skip to content

Commit

Permalink
Update intro
Browse files Browse the repository at this point in the history
  • Loading branch information
sajith committed Apr 23, 2024
1 parent d2f6e1d commit f6cce89
Showing 1 changed file with 10 additions and 8 deletions.
18 changes: 10 additions & 8 deletions theme1/PE103/vcs.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,12 +31,14 @@ with a chaotic mess which achieves the above goals in a poorer manner.
You will likely resort to several almost-same-but-not-quite files
variously named like so:

<!-- - `notebook.ipynb` -->
<!-- - `notebook-2024-05-01.ipynb` -->
<!-- - `notebook-2024-05-01-final.ipynb` -->
<!-- - `notebook-working.ipynb` -->
<!-- - `notebook-test.ipynb` -->
<!-- - `notebook-final.ipynb` -->
- `notebook.ipynb`
- `notebook-2024-05-01.ipynb`
- `notebook-2024-05-01-final.ipynb`
- `notebook-working.ipynb`
- `notebook-test.ipynb`
- `notebook-final.ipynb`

Or a situation depicted by a famous PHD Comics [strip][notfinal]:

[![](http://www.phdcomics.com/comics/archive/phd101212s.gif)][notfinal]

Expand All @@ -47,8 +49,8 @@ system. That might work in the simple cases, but it will soon break
down as you do more work on your project.

You want to avoid the cognitive overload of dealing with messy schemes
based on file names. You want to do is learn to use a version control
system properly.
based on file names. You want to use a version control system
properly.


## Version control in practice: Git
Expand Down

0 comments on commit f6cce89

Please sign in to comment.