Leave about 30 minutes at the start of each workshop and another 15 mins at the start of each session for technical difficulties like WiFi and installing things (even if you asked students to install in advance, longer if not).
There can be difficulties linking git to RStudio depending on the operating system and the version of the operating system. To make sure Git is properly installed and configured, the learners should go to the Options window in the RStudio application.
which git and you will get a path to the git executable. In the “Git executable” window you may have difficulties finding the directory since OS X hides many of the operating system files. While the file selection window is open, pressing “Command-Shift-G” will pop up a text entry box where you will be able to type or paste in the full path to your git executable: e.g. /usr/bin/git or whatever else it might be.C:/Program Files/Git/bin/git.exe.To prevent the learners from having to re-enter their password each time they push a commit to GitHub, this command (which can be run from a bash prompt) will make it so they only have to enter their password once:
$ git config --global credential.helper 'cache --timeout=10000000'
The easiest way to get the data used in this lesson during a workshop is to have attendees run the following:
git remote add data https://github.com/resbaz/r-novice-gapminder-files
git pull data master
If Git is not being taught as part of the workshop the raw data can be downloaded from gapminder-FiveYearData and gapminder-FiveYearData-Wide.
Attendees can use the File - Save As dialog in their browser to save the file.
Make sure to emphasize good practices: put code in scripts, and make sure they’re version controlled. Encourage students to create script files for challenges.
If you’re working in a cloud environment, get them to upload the gapminder data after the second lesson.
Make sure to emphasize that matrices are vectors underneath the hood and data frames are lists underneath the hood: this will explain a lot of the esoteric behaviour encountered in basic operations.
Vector recycling and function stacks are probably best explained with diagrams on a whiteboard.
Be sure to actually go through examples of an R help page: help files can be intimidating at first, but knowing how to read them is tremendously useful.
Be sure to show the CRAN task views, look at one of the topics.
There’s a lot of content: move quickly through the earlier lessons. Their extensiveness is mostly for purposes of learning by osmosis: so that their memory will trigger later when they encounter a problem or some esoteric behaviour.
Key lessons to take time on:
Don’t worry about being correct or knowing the material back-to-front. Use mistakes as teaching moments: the most vital skill you can impart is how to debug and recover from unexpected errors.