-
Notifications
You must be signed in to change notification settings - Fork 34
/
instructors.html
58 lines (56 loc) · 3.61 KB
/
instructors.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="generator" content="pandoc">
<title>Lesson Title</title>
<link rel="shortcut icon" type="image/x-icon" href="/favicon.ico" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="stylesheet" type="text/css" href="css/bootstrap/bootstrap.css" />
<link rel="stylesheet" type="text/css" href="css/bootstrap/bootstrap-theme.css" />
<link rel="stylesheet" type="text/css" href="css/swc.css" />
<link rel="alternate" type="application/rss+xml" title="Software Carpentry Blog" href="http://software-carpentry.org/feed.xml"/>
<meta charset="UTF-8" />
<!-- HTML5 shim, for IE6-8 support of HTML5 elements -->
<!--[if lt IE 9]>
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body class="lesson">
<div class="container card">
<article>
<div class="row">
<div class="col-md-10 col-md-offset-1">
<a href="index.html"><h1 class="title">Lesson Title</h1></a>
<h2 class="subtitle">Instructor’s Guide</h2>
<h2 id="timing">Timing</h2>
<p>Leave about 30 minutes at the start of each workshop and another 15 mins at the start of each sesson for technical difficulties like WiFi and installing things (even if you asked students to install in advance, longer if not).</p>
<h2 id="pulling-in-data">Pulling in data</h2>
<p>The easiest way to get the data used in this lesson during a bootcamp is to have attendees run the following:</p>
<pre class="shell"><code>git remote add data https://github.com/resbaz/r-novice-gapminder-files
git pull data master</code></pre>
<h2 id="overall">Overall</h2>
<p>Make sure to emphasise good practices: put code in scripts, and make sure they’re version controlled. Encourage students to create script files for challenges.</p>
<p>If you’re working in a cloud environment, get them to upload the gapminder data after the second lesson.</p>
<p>Make sure to emphasise 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.</p>
<p>Vector recycling and function stacks are probably best explained with diagrams on a whiteboard.</p>
<p>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.</p>
<p>Be sure to show the CRAN task views, look at one of the topics.</p>
<p>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 encouter a problem or some esoteric behaviour.</p>
<p>Key lessons to take time on:</p>
<ul>
<li>Data subsetting - conceptually difficult for novices</li>
<li>Functions - learners especially struggle with this</li>
<li>Data structures - worth being thorough, but you can go through it quickly.</li>
</ul>
<p>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.</p>
</div>
</div>
</article>
</div>
<!-- Javascript placed at the end of the document so the pages load faster -->
<script src="http://software-carpentry.org/v5/js/jquery-1.9.1.min.js"></script>
<script src="css/bootstrap/bootstrap-js/bootstrap.js"></script>
<script src='https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML'></script>
</body>
</html>