-
Notifications
You must be signed in to change notification settings - Fork 12
/
teacher-training.slide
271 lines (161 loc) · 8.83 KB
/
teacher-training.slide
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
GoBridge Workshop - Teacher training
GoBridge
support@golangbridge.org
http://golangbridge.org
@golangbridge
* What is this?
This slide deck is a tool to facilitate conversations about teaching best practices and challenges, specifically for GoBridge workshops.
- Discussion is key!
- Don't let the presenter(s) do all the talking!
* Why GoBridge?
We're making tech more diverse and more welcoming!
* How?
- We throw super-welcoming, fun, free workshops.
- We provide a wealth networking opportunities for students and volunteers.
- We help our volunteers become more empathetic and better communicators.
* Introductions
Who are you?
* Typical GoBridge Schedule
- Saturday's schedule, often:
- 9-9:30am: Check-in, coffee, bagels
- 9:30-10am: Opening presentation
- 10am-12:30pm: Class!
- 12:30-1:30pm: Lunch
- 1:30pm-4:30pm: Class! (with a break sometime mid-afternoon)
- Sunday's schedule, often:
- 9-9:30am: Check-in, coffee, bagels
- 10am-12:30pm: Class!
- 12:30-1:30pm: Lunch
- 1:30pm-4:30pm: Class! (with a break sometime mid-afternoon)
- 4:30-5:00pm: Closing presentation & retros
- 5:00pm-late: After-party
* Is GoBridge Open Source?
- WHY YES, THANK YOU FOR ASKING!
- GoBridge IS VERY OPEN SOURCE!
All the materials you're using were created by volunteers, and are on GitHub for forking and editing and using!
If you see something that could be better, make a pull request. Pull requests are the lifeblood of GoBridge.
If you don't know how to make one, we'll help!
* How to make your class awesome
We've made three quasi-arbitrary categories of ways to make your class awesome.
We want our students to feel:
- socially comfortable
- technically capable
- like you are approachable and can help solve their problems
* Discussion: Social Comfort
Imagine:
- You're trying to do something difficult
- You're in a group of strangers, many of whom know how to do it better than you
- You've tried before but got lost or bored or confused
- You don't feel like you can articulate your thoughts and questions
- You don't know the right names for anything
When was the last time you felt this way?
How can we help make this easier?
How can you help people feel socially comfortable?
* Social Comfort (Ideas)
* Introductions
- Include name, profession, why are you here / goals for today's class, and something silly.
- Don't rush, even if you have a big class.
- If someone joins the class late, ask them to introduce themselves.
* Icebreakers
- Name games! Admit up front that most people are bad at learning new names.
- Get people talking. The more comfortable they are at talking, the more likely they'll speak up when they don't understand something, or to answer someone else's question.
* Social Comfort (More Ideas)
Try to suppress your (understandable) culturally-influenced sexism
- Don't hit on people. No sexual advances. None. Even at the after-party.
- Don't make sexist jokes. Or racist, classist, or ableist jokes. Call people out if they do. A simple "That's not funny" and moving on quickly with the conversation will often suffice.
- Don't make gender-based generalizations ("Women are better at X, because ...")
- Don't make references to people's bodies or state your opinion of them.
- Don't use slurs.
* Discussion: Technical Capability
- How can you help people feel technically capable?
- What kinds of insecurities might your student have?
- How can you bolster their confidence?
* Technical Capability (Ideas)
Explain that:
- Even professional developers are constantly learning new technologies, so being confused is normal.
- Initial code is often terrible: don't feel bad, just refactor!
- Mistakes == Learning!
* Dealing with technical concepts:
- Define technical terms! Several times if needed!
- Assume anyone you're teaching has zero knowledge but infinite intelligence.
- Remember people's professional and code backgrounds (QA, DBA, C++, Java, JS) and relate where possible. If they are a cook, try a cooking analogy.
* Technical Capability (More Ideas)
Encourage collaboration and interaction:
- Explicitly encourage students to try to answer each other's questions.
- If a question is asked, ask if anyone in the class thinks they can explain.
- Be especially encouraging of the first few questions, to try to get things rolling.
- Good responses to questions: "I'm glad you asked!" or "I actually wondered that, too." or "Great question!"
* Be Super Positive, Always
- Students have diverse backgrounds. Appreciate this fact.
- If they aren't getting a concept, avoid anything that might shame them.
- Don't be surprised when someone hasn't heard of something before.
- Don't grab anyone's keyboard. Avoid taking over unless you think it's *really- necessary. Ask before you do. "Mind if I drive for a sec?" But really, don't.
* Technical Capability (Even More Ideas)
Walk the Middle Path:
- Don't go too deep for your class level, but also, don't gloss over things.
- When trying to be accurate, it's easy to go down a rabbit hole of specificity. Avoid.
- Work with the TAs to make sure no one goes down that rabbit hole. Accountability!
- Explain the big picture of a command *before* they type it in:
- i.e., before typing the command to deploy to Heroku, explain the difference between localhost and Heroku.
* Discussion (Do you know what's up?)
- How can you help people feel like you know what's going on?
- What are things you can do to help the students trust you?
- What are some things to avoid?
* Establish a few ground rules
- Questions are always welcome, even if the student thinks it might be dumb.
- Explain that if someone has trouble (e.g., not getting the expected output), the TAs will help troubleshoot.
* Know What's Up (More Ideas)
Don't be afraid to:
- Call on people! By name!
- Correct people if they're wrong. Be polite and encouraging. For instance:
- "Well, this might work better and this is why."
- "Can you explain how you came to that conclusion?"
- "Does anyone have a different answer?"
- Ask yourself questions and answer them.
* Know What's Up (Even More Ideas)
Pace yourself!
- Don't go too fast. You will probably go too fast. Check in occasionally to ensure everyone is still with you.
- You can say the same thing THREE TIMES and it will not be boring yet.
- When you ask a question, wait TEN WHOLE SECONDS before saying anything else. People need time to think.
- Don't let the most advanced students dictate the pacing or answer all the questions.
* Discussion: Challenges
Talk about what problems you might anticipate, and what to do about them.
* Some issues:
- Student is disruptive
- Student is disengaged
- TA is not helping
* What's a TA?
- At GoBridge, a TA is a volunteer who isn't leading the class.
- If you're volunteering at your first GoBridge workshop, you should probably be a TA.
- Sometimes they are the technical experts (rather than the teacher), sometimes not.
- TAs often explain specific concepts for the class or teach a couple of sections to give the teacher a break from talking.
* Discussion: TAs
TAs: How can you best utilize the AWESOME POWER that is a TA?
* TAs (Some Ideas)
- TAs can ask questions to encourage students to speak up.
- Ask your TA to explain a concept; they may be more technically advanced than you!
- TAs can help people who get lost.
- Co-teaching is also an option if you feel like you can tag-team. There doesn't have to be a hierarchy.
- If someone falls behind, the TA can take them out of the room to do some 1-on-1, if there's another TA in the room.
* Discussion: Comprehension
- How can you tell if they understand the words you're saying?
- What are good questions to ask to check comprehension?
- What did your favorite teachers do to gauge understanding?
* Student Comprehension (Some Ideas)
- Pay attention to body language.
- People ask questions most often when they are actively processing material. If they aren't, it might be that the material is too easy or hard. Try to figure out which it is!
* Calling on people
- Calling on people makes the class more interactive and engaging, and less lecture-y.
- Don't always ask questions to the whole class: call on individuals by name.
- Consider breaking the class into two teams and addressing questions to teams.
- Ask people what they expect a command to produce BEFORE you hit enter.
- Ask "How would you do _this_ " or "If I wanted to do \#\{that\}, what would I do?"
* Keep in mind:
- There will be people with _all_ kinds of computers.
- Even though Windows is not a usual development environment, we're here to encourage people and meet them wherever they are right now.
- Do NOT say bad things about Windows, even if it's frustrating.
- If you're not sure about something, grab another volunteer.
* Very Important, Very Practical Things
- You need to read the curriculum you are teaching through and through, beginning to end, before teaching it.
- First workshop? Be a TA!
We need your help! Thank you!!!