Skip to content

Commit 4cf7a1a

Browse files
tjgrathwelltjgrathwell
committed
Merge pull request railsbridge#142 from lilliealbert/new_teacher_training
add updated teacher training slides
2 parents a2c92d8 + d3a9a26 commit 4cf7a1a

File tree

2 files changed

+153
-0
lines changed

2 files changed

+153
-0
lines changed

‎sites/workshop/more_teacher_training.deck.md

+152
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,152 @@
1+
# RailsBridge Teacher Training
2+
3+
# RailsBridge Mission
4+
Let's make tech more diverse and more welcoming!
5+
6+
### How?
7+
* Workshops
8+
* Bug Mashes
9+
* Mentorship
10+
11+
# Introductions
12+
### Who are you?
13+
* Name
14+
* What do you do for money? Who gives you that money?
15+
* What's your favorite structure in the Bay Area?
16+
17+
# How to make your class awesome
18+
Three buckets, lots of ways:
19+
### Help people feel:
20+
* socially comfortable
21+
* technically capable
22+
* like you know what's going on
23+
24+
# DISCUSSION (Social Comfort)
25+
## How can you help people feel socially comfortable?
26+
27+
# OUR IDEAS (Socially Comfortable 1)
28+
### Helping people feel socially comfortable:
29+
30+
### Introductions
31+
* Definitely cover name, profession, why are you here, and something silly
32+
* Don't rush, even if you have a big class.
33+
* If someone joins the class late, ask them to introduce themselves
34+
35+
### Icebreakers
36+
* Help people learn each other's name -- admit upfront that no one is good at learning new names
37+
* 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
38+
39+
# OUR IDEAS (Socially Comfortable 2)
40+
### Try to suppress your (understandable) culturally-influenced sexism
41+
* Don't hit on people. No sexual advances. None.
42+
* Don't make sexist jokes. Or racist, classist, or ableist jokes while you're at it. Call people out if they do.
43+
* Don't make gender-based generalizations ("Women are better at this task X, because ...")
44+
* Don't treat women as delicate flowers, do treat them like normal people.
45+
* Don't use slurs (bitch is a slur, btw).
46+
47+
# DISCUSSION (Technical Capability)
48+
## How can you help people feel technically capable?
49+
50+
# OUR IDEAS (Technically Capable 1)
51+
### Set the tone:
52+
* Explain up front that even professional developers are constantly learning new technologies.
53+
* Explain that mistakes are how we learn, and most mistakes seem silly in retrospect.
54+
* Before class, ask your TAs to ask questions if concepts don't seem clear.
55+
56+
### Explaining technical concepts:
57+
* Avoid jargon and explain words when jargon is unavoidable.
58+
* Assume anyone you're teaching has zero knowledge but infinite intelligence.
59+
* Remember people's professional and code backgrounds (QA, DBA, C++, Java, JS) and relate where possible.
60+
61+
# OUR IDEAS (Technically Capable 2)
62+
### Encourage collaboration and interaction
63+
* Explicitly say that student should try to answer each other's questions, that it's a really great way to reinforce learning.
64+
* If a question is asked, ask if anyone in the class thinks they can explain.
65+
* Be especially encouraging of the first few questions, to try to get things rolling.
66+
* You could say things like "I'm glad you asked!" or "I actually wondered that, too." or "Great question!"
67+
* Hand someone the whiteboard marker if it exists.
68+
69+
### Don't talk down or be negative
70+
* Students have diverse backgrounds
71+
* If they aren't getting a concept, avoid anything that might shame them.
72+
* Don't be surprised when someone hasn't heard of something before.
73+
* Don't grab anyone's keyboard. Avoid taking over unless you think it's *really* necessary.
74+
75+
# OUR IDEAS (Technically Capable 3)
76+
### Don't go too deep for your class level, but also, don't gloss over things
77+
* Basically: walk the middle path
78+
* When you're trying to be accurate, it's easy to go down a rabbit hole of specificity. Avoid.
79+
* Talk to your TAs about avoiding that, and how you can hold each other accountable.
80+
* Explain the big picture of a command *before* they type it in.
81+
* So before typing the command to deploy to Heroku, explain the difference between localhost and Heroku.
82+
83+
# DISCUSSION (DO YOU KNOW WHAT'S GOING ON?)
84+
## How can you help people feel like you know what's going on?
85+
86+
# OUR IDEAS (KNOW WHAT'S UP 1)
87+
### Introduce yourself well
88+
* Tell your story.
89+
* Talk about why you like programming and teaching.
90+
* Talk about why you care enough to do this.
91+
* Don't brag.
92+
93+
### Know what's going on
94+
* Cover logistics at the beginning of class
95+
* Planned breaks, lunch time
96+
* Remind students that there is a closing presentation at the end
97+
* Tell them where the bathroom is
98+
* Tell them where the afterparty is
99+
100+
# OUR IDEAS (KNOW WHAT'S UP 2)
101+
### Establish ground rules
102+
* Questions are always welcome, even if the student thinks it might be dumb
103+
* Explain that if someone has trouble not getting the expected output, the TAs will help troubleshoot
104+
* If anyone wants to switch classes, tell them they should feel TOTALLY COMFORTABLE switching at any point.
105+
106+
### Don't be afraid to:
107+
* Call on people!
108+
* Correct people (gently and politely) if they're wrong.
109+
* Answer questions that haven't been asked yet.
110+
111+
# OUR IDEAS (KNOW WHAT'S UP 3)
112+
### Try to have good pacing
113+
* Don't go too fast. You will go too fast.
114+
* You can say the same thing THREE TIMES and it will not be boring yet. (Unless it was boring initially. JK.)
115+
* When you ask a question, wait TEN WHOLE SECONDS before saying anything else. People need time to think.
116+
* Don't let the most advanced students dictate the pacing
117+
118+
# DISCUSSION
119+
Talk about what problems you might anticipate, and what to do about the.
120+
121+
# OUR IDEAS
122+
### Some issues:
123+
* Student in the wrong class level
124+
* Student is disruptive
125+
* Student is disengaged
126+
* TA is not helping
127+
128+
# DISCUSSION
129+
TAs: What are they good for? Absolutely everything!!!
130+
131+
# OUR IDEAS
132+
* Ask your TA to explain a concept
133+
* TAs can help people who get lost
134+
* Encourage your TAs to jump in to help explain something if you're struggling
135+
* TAs can ask the first question to encourage students to speak up.
136+
137+
# DISCUSSION
138+
How can you tell if they understand the words you're saying?
139+
140+
# OUR IDEAS
141+
* Don't ask yes/no questions ... they are too easy.
142+
* Pay attention to body language
143+
* Ask "How would you do \{this\}?" or "If I wanted to do \{that}, what would I do?"
144+
145+
### Calling on people
146+
* Don't be a jerk
147+
* ???
148+
149+
# SOURCES
150+
* HOWTO Encourage Women in Linux http://tldp.org/HOWTO/Encourage-Women-Linux-HOWTO/x168.html#AEN243
151+
152+

‎sites/workshop/workshop.md

+1
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@
1414

1515
## Workshop Prep:
1616
* [Teacher Training](teacher_training)
17+
* [Updated Teacher Training Slides (as of 1/16/13)](more_teacher_training)
1718

1819

1920
See the [toc] link in the top right for a full table of contents.

0 commit comments

Comments
 (0)