-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathindex.html
301 lines (260 loc) · 12.2 KB
/
index.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
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
---
layout: workshop
root: .
venue: "University of Auckland" # brief name of host site without address (e.g., "Euphoric State University")
address: "Conference Centre Building, 22 Symonds Street, Auckland" # street address of workshop (e.g., "123 Forth Street, Blimingen, Euphoria")
country: nz # country (lowercase two-letter ISO code such as "fr" - see https://en.wikipedia.org/wiki/ISO_3166-1)
language: en # language (lowercase two-letter ISO code such as "fr" - see https://en.wikipedia.org/wiki/ISO_639-1)
latlng: "-36.853647,174.769403" # fractional latitude and longitude (e.g., "41.7901128,-87.6007318"; you can use http://www.latlong.net/)
humandate: Jan 28-29, 2016 # human-readable date (e.g., "Feb 17-18, 2020")
humantime: 9:00 am - 5:00 pm # human-readable time (e.g., "9:00 am - 4:30 pm")
startdate: 2016-01-28 # use YYYY-MM-DD format like "2015-01-01"
enddate: 2016-01-29 # use YYYY-MM-DD format like" 2015-01-02"
trainer: ["Aleksandra Pawlik", "John Rugis"] # list of names like ["Kay McNulty", "Betty Jennings", "Betty Snyder"]
helper: ["TBA"] # list of names like above
contact: "[email protected]" # contact email address for workshop organizer, such as "[email protected]"
etherpad: http://pad.software-carpentry.org/2016-01-28-Auckland-Instructor-Training # optional (insert the URL for your Etherpad if you're using one)
eventbrite: # optional (insert the alphanumeric key for Eventbrite registration, e.g., "1234567890AB")
prep-repository: https://github.com/carpentry-instructor-training/2016-01-28-training-prep # optional (insert the URL to the repository for the preparation PR exercise
---
<!--
HEADER
Edit the values in the block above to be appropriate for your workshop.
If the value is not 'true', 'false', 'null', or a number, please use
double quotation marks around the value, unless specified otherwise.
And run 'tools/check' *before* committing to make sure that changes are good.
-->
<!--
EVENTBRITE
This block includes the Eventbrite registration widget if
'eventbrite' has been set in the header. You can delete it if you
are not using Eventbrite, or leave it in, since it will not be
displayed if the 'eventbrite' field in the header is not set.
-->
{% if page.eventbrite %}
<iframe
src="https://www.eventbrite.com/tickets-external?eid={{page.eventbrite}}&ref=etckt"
frameborder="0"
width="100%"
height="248px"
scrolling="auto">
</iframe>
{% endif %}
<h2>Workshop description</h2>
<!--
INTRODUCTION
Edit the general explanatory paragraph below if you want to change
the pitch.
-->
<p>
The New Zealand eScience Infrastructure (NeSI) is pleased to announce its sponsorship of a Software Carpentry instructor
training event in New Zealand.
This workshop covers the basics of educational psychology and instructional design, and looks at how to use these ideas
in both intensive workshops and regular classes. The workshop is a mix of lectures and hand-on lessons where you
practice giving a short lesson using approaches learned and implement some of the teaching techniques which we will discuss.
This is training for teaching, not technical training; you do not need any particular technical background,
and we will not be teaching that.This workshop is based on the constantly revised and updated
<a href="http://swcarpentry.github.io/instructor-training/">curriculum</a>.
</p>
<p>
<strong>Who:</strong>
The course is aimed at everyone who is interested in becoming a better teacher. In particular,
this trainig is aimed at those who want to become Software and Data Carpentry instructors, run
workshops and contribute to the Carpentry training materials.
<p><strong>You don't have to be currently an instructor or a teacher to attend this workshop. But you do need to be
willing and committed to become one and to improve your teaching techniques. </strong></p>
</p>
<!--
LOCATION
This block displays the address and links to maps showing directions
if the latitude and longitude of the workshop have been set. You
can use http://itouchmap.com/latlong.html to find the lat/long of an
address.
-->
{% if page.latlng %}
<p>
<strong>Where:</strong>
{{page.address}}.
Get directions with
<a href="//www.openstreetmap.org/?mlat={{page.latlng | replace:',','&mlon='}}&zoom=16">OpenStreetMap</a>
or
<a href="//maps.google.com/maps?q={{page.latlng}}">Google Maps</a>.
</p>
{% endif %}
<!--
SPECIAL REQUIREMENTS
Modify the block below if there are any special requirements.
-->
<p>
<strong>Requirements:</strong>
Participants should bring a laptop that is wifi Internet capable and has a functioning browser.
If you have it, a specialized device for recording audio and video
(mobile phones and laptops are OK) - throughout the two days,
we are going to record one another teaching in pairs or threes.
It does not have to be high-quality,
but it should be good enough that you can understand what someone is saying.
<p><em>Also, make sure you read the
<a href="#preparation">Preparation</a> section below.</em> You will also receive some further
information before the workshop so please check your email.</p>
All paricipants are also required to abide by
Software Carpentry's <a href="{{site.swc_site}}/conduct.html">Code of Conduct</a>.
</p>
<!--
CONTACT EMAIL ADDRESS
Display the contact email address set in the header. If an address
isn't set in the header, the Software Carpentry admin address is
used.
-->
<p>
<strong>Contact</strong>:
Please mail
{% if page.contact %}
<a href='mailto:{{page.contact}}'>{{page.contact}}</a>
{% else %}
<a href='mailto:{{site.contact}}'>{{site.contact}}</a>
{% endif %}
for more information.
</p>
<hr/>
<!--
SCHEDULE
Show the workshop's schedule. Edit the items and times in the table
to match your plans. You may also want to change 'Day 1' and 'Day
2' to be actual dates or days of the week.
-->
<h2>Schedule</h2>
<div class="row">
<div class="col-md-6">
<h3>Day 1</h3>
<table class="table table-striped">
<tr> <td>09:00</td> <td>Welcome and introductions</td></tr>
<tr> <td>09:30</td> <td>Overview: key concepts and training goals</td></tr>
<tr> <td>10:00</td> <td>Formative vs. summative assessment</td></tr>
<tr> <td>10:30</td> <td>Coffee break</td></tr>
<tr> <td>11:00</td> <td>Teaching as performance art</td> </tr>
<tr> <td>12:00</td> <td>Lunch break</td></tr>
<tr> <td>13:00</td> <td>Discussion on the exercise on teaching as performance art</td> </tr>
<tr> <td>14:00</td> <td>Concept maps</td> </tr>
<tr> <td>14:30</td> <td>Coffee break</td> </tr>
<tr> <td>15:00</td> <td> Concept maps - continued</td> </tr>
<tr> <td>16:00</td> <td>Motivation and demotivation. Diversity. Indifference.</td> </tr>
<tr> <td>16:45</td> <td>Wrap-up</td> </tr>
<tr> <td>17:00</td> <td>Close</td> </tr>
</table>
</div>
<div class="col-md-6">
<h3>Day 2</h3>
<table class="table table-striped">
<tr> <td>09:00</td> <td>Recap and homework review<br></td> </tr>
<tr> <td>09:30</td> <td>Alternative formative assessment techniques</td> </tr>
<tr> <td>10:30</td> <td>Coffee break</td> </tr>
<tr> <td>11:00</td> <td>Live coding and active learning</td> </tr>
<tr> <td>12:00</td> <td>Lunch break</td> </tr>
<tr> <td>13:00</td> <td>Overview of Software and Data Carpentry infrastructure</td> </tr>
<tr> <td>13:30</td> <td>Setting up and running a workshop</td> </tr>
<tr> <td>14:30</td> <td>Coffee break</td> </tr>
<tr> <td>15:00</td> <td>Overview of existing materials; how to contribute</td> </tr>
<tr> <td>16:00</td> <td>Next setps</td> </tr>
<tr> <td>16:45</td> <td>Wrap-up</td> </tr>
<tr> <td>17:00</td> <td>Close</td> </tr>
</table>
</div>
</div>
<!--
ETHERPAD
At `_misc/etherpad.txt` you will find a template for the etherpad.
Display the Etherpad for the workshop. You can set this up in
advance or on the first day; either way, make sure you push changes
to GitHub after you have its URL. To create an Etherpad, go to
http://pad.software-carpentry.org/YYYY-MM-DD-site
where 'YYYY-MM-DD-site' is the identifier for your workshop,
e.g., '2015-06-10-esu'.
-->
{% if page.etherpad %}
<p>
<strong>Etherpad:</strong> <a href="{{page.etherpad}}">{{page.etherpad}}</a>.
<br/>
We will use this Etherpad for chatting, taking notes, and sharing URLs and bits of code.
</p>
{% endif %}
<hr/>
<!--
Syllabus
Show what topics will be covered.
-->
<h2>Syllabus</h2>
<div class="row">
<div class="col-md-6">
<h3>Cognitive development and models</h3>
<ul>
<li><a href="http://swcarpentry.github.io/instructor-training/02-cognition.html">Reference</a></li>
</ul>
</div>
<div class="col-md-6">
<h3>Mental models</h3>
<ul>
<li><a href="http://swcarpentry.github.io/instructor-training/01-models.html">Reference.</a></li>
</ul>
</div>
<div class="col-md-6">
<h3>Lesson design</h3>
<ul>
<li><a href="http://swcarpentry.github.io/instructor-training/03-design.html">Reference.</a></li>
</ul>
</div>
</div>
<hr/>
<h2 id="preparation" name="preparation">Preparation</h2>
<p>In preparation for the training we would like to ask you to:
<ol>
<li> Watch one of the following videos from Software Carpentry workshops
<a href="https://vimeo.com/139316669">https://vimeo.com/139316669</a>
<strong> or</strong> <a href="https://vimeo.com/139181120">https://vimeo.com/139181120</a>
and put a 3-4 sentences feedback to <a href="{{page.etherpad}}">{{page.etherpad}}</a>.
</li>
<li> Complete a small task:
<ul>
<li> If you want to teach Software Carpentry, please submit a small pull request to
<a href="{{page.prep-repository}}">this repository</a>
Your pull request should contain one file (and one file only) called "your_name.txt"
(e.g., marie_curie.txt or alan_turing.txt). This file should contain a sentence or
two that describes the type of work you do. You will submit the name of this file
as part of your application. <br/>
Help on creating pull requests can be found at <a href="https://help.github.com/articles/using-pull-requests/">
https://help.github.com/articles/using-pull-requests</a>.
If you need assistance, please mail [email protected].
</li>
<li>
If you want to teach <strong>only</strong> Data Carpentry, please propose a short exercise for
<a href="http://www.datacarpentry.org/lessons/">the existing lessons</a>
by submitting it via <a href="http://goo.gl/forms/YRw2LHYnVo">this form</a>.
</li>
</ul>
</li>
<li>
Read:
<ul>
<li><a href="http://files.software-carpentry.org/training-course/2013/08/p34-porter.pdf">
Porter et al's "Success in Introductory Programming: What Works?"</a>
, which is a good recent summary of results specific to teaching programming.</li>
<li><a href="http://files.software-carpentry.org/training-course/2012/08/guzdial.pdf">
Mark Guzdial's "Top 10 Myths About Teaching Computer Science",</a>
which is a nice overview of things that are not true, but are widely believed</li>
</ul>
</li>
</ol>
</p>
<p> If you are interested in doing more reading:
<ol>
<li><a target="_blank"href="http://www.amazon.com/Teaching-What-You-Dont-Know/dp/0674066170">Huston's
"Teaching What You Don't Know"</a> is a lot of fun - many will recognize themselves in these
stories.</li>
<li> <a target="_blank"href="http://www.amazon.com/Building-Better-Teacher-Teaching-Everyone/dp/0393081591">"Building
a Better Teacher"</a>, is a well-written look at
why educational reforms in the past 50 years have mostly failed, and about what we should be doing instead.</li>
<li><a target="_blank"
href="http://www.amazon.com/How-Learning-Works-Research-Based-Jossey-Bass/dp/0470484101/">Susan A. Ambrose's "How
Learning Works"</a> is the best summary going of research in education.
It is full of useful insights, and a lot of how we teach is based on the findings it reports.</li>
</ol>
</p>