Skip to content

Commit f0728f7

Browse files
socksysocksy
committed
Compiled coaches training changes to HTML
1 parent 8ec3a71 commit f0728f7

File tree

1 file changed

+124
-107
lines changed

1 file changed

+124
-107
lines changed

‎coaches_training.deck.html‎

Lines changed: 124 additions & 107 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ <h3>Don't let the presenter(s) do all the talking!</h3>
4848
<section class="slide" id="code_of_conduct">
4949
<h2>Code of Conduct</h2>
5050

51-
<p>The Berlin Code of Conduct (<a href="berlincodeofconduct.org">berlincodeofconduct.org</a>) outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.</p>
51+
<p>The Berlin Code of Conduct (<a href="berlincodeofconduct.org">berlincodeofconduct.org</a>) outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.</p>
5252

5353
<h3>Expected Behavior</h3>
5454

@@ -89,19 +89,14 @@ <h2>Introductions</h2>
8989
<h3>Who are you?</h3>
9090

9191
<ul>
92-
<li>What's your name?</li>
93-
<li>What are your pronouns?</li>
94-
<li>Have you been to a ClojureBridge or similar workshops before? How many?</li>
95-
<li>What's your favorite place in Berlin?</li>
96-
<li>What's the most non-coding thing you do?</li>
92+
<li>What's your name and pronouns?</li>
93+
<li>Have you been to a ClojureBridge or similar workshops before?</li>
9794
</ul>
9895

9996
</section>
10097
<section class="slide" id="whats_a_clojurebridge">
10198
<h2>What's a ClojureBridge?</h2>
10299

103-
<p>Raise your hand if you've been to a workshop before!</p>
104-
105100
<h3>RailsBridge Fun Facts</h3>
106101

107102
<ul>
@@ -140,7 +135,7 @@ <h2>Installfest!</h2>
140135

141136
<p>NightCode is pretty easy to install, as it's just an executable JAR. We'll have a couple thumb drives to go around.</p>
142137

143-
<p>Please actually create and run a Quil project, so all dependencies are downloaded and available.</p>
138+
<p>Please actually create and run a Quil project, so all dependencies are downloaded and available – this has caused problems before!</p>
144139

145140
<h4>Keep in mind:</h4>
146141

@@ -151,6 +146,28 @@ <h4>Keep in mind:</h4>
151146
<li>If you're not sure about something, grab another volunteer.</li>
152147
</ul>
153148

149+
</section>
150+
<section class="slide" id="on_that_note">
151+
<h2>On that note...</h2>
152+
153+
<ul>
154+
<li>Don't be negative about technologies, even if you're certain they're the work of the devil</li>
155+
<li>PHP is fine, Windows is fine, VisualBasic is fine</li>
156+
<li>Appreciate that different technologies have different trade-offs. Being easily accessible is one of them.</li>
157+
</ul>
158+
159+
</section>
160+
<section class="slide" id="try_to_suppress_your_understandable_culturallyinfluenced_sexism">
161+
<h2>Try to suppress your (understandable) culturally-influenced sexism</h2>
162+
163+
<ul>
164+
<li>Don't hit on people. No sexual advances. This extends to the after-party.</li>
165+
<li>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.</li>
166+
<li>Don't make gender-based generalizations ("Women are better at X, because ...")</li>
167+
<li>Don't make references to people's bodies or state your opinion of them.</li>
168+
<li>Don't use slurs.</li>
169+
</ul>
170+
154171
</section>
155172
<section class="slide" id="typical_clojurebridge_schedule">
156173
<h2>Typical ClojureBridge Schedule</h2>
@@ -245,6 +262,66 @@ <h4>How can you help people feel socially comfortable?</h4>
245262

246263
<p>DISCUSS!</p>
247264

265+
</section>
266+
<section class="slide" id="discussion_do_you_know_whats_up">
267+
<h2>Discussion (Do you know what's up?)</h2>
268+
269+
<h4>How can you help people feel like you know what's going on?</h4>
270+
271+
<h4>What are things you can do to help the students trust you?</h4>
272+
273+
<h4>What are some things to avoid?</h4>
274+
275+
<p>DISCUSS!</p>
276+
277+
</section>
278+
<section class="slide" id="discussion_technical_capability">
279+
<h2>Discussion: Technical Capability</h2>
280+
281+
<h3>How can you help people feel technically capable?</h3>
282+
283+
<h3>What kinds of insecurities might your student have?</h3>
284+
285+
<h3>How can you bolster their confidence?</h3>
286+
287+
<p>DISCUSS!</p>
288+
289+
</section>
290+
<section class="slide" id="discussion_challenges">
291+
<h2>Discussion: Challenges</h2>
292+
293+
<p>Talk about what problems you might anticipate, and what to do about them.</p>
294+
295+
<h4>Some issues:</h4>
296+
297+
<ul>
298+
<li>Student is in the wrong class level</li>
299+
<li>Student is disruptive</li>
300+
<li>Student is disengaged</li>
301+
</ul>
302+
303+
<p>DISCUSS!</p>
304+
305+
</section>
306+
<section class="slide" id="discussion_coaching">
307+
<h2>Discussion: Coaching</h2>
308+
309+
<h4>What are the benefits of having two coaches in a group?</h4>
310+
311+
<h4>How can you divide the roles between the coaches?</h4>
312+
313+
<h4>How can you get a good dynamic between the whole team, both attendees and coaches?</h4>
314+
315+
<p>DISCUSS!</p>
316+
317+
</section>
318+
<section class="slide" id="what_we_came_up_with">
319+
<h2>What we came up with</h2>
320+
321+
<ul>
322+
<li>So now you've been through these discussions, this is what we came up with!</li>
323+
</ul>
324+
248325
</section>
249326
<section class="slide" id="social_comfort_ideas">
250327
<h2>Social Comfort (Ideas)</h2>
@@ -266,18 +343,7 @@ <h4>Icebreakers</h4>
266343

267344
</section>
268345
<section class="slide" id="social_comfort_more_ideas">
269-
<h2>Social Comfort (More Ideas)</h2>
270-
271-
<h4>Try to suppress your (understandable) culturally-influenced sexism</h4>
272-
273-
<ul>
274-
<li>Don't hit on people. No sexual advances. None. Even at the after-party.</li>
275-
<li>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.</li>
276-
<li>Don't make gender-based generalizations ("Women are better at X, because ...")</li>
277-
<li>Don't make references to people's bodies or state your opinion of them.</li>
278-
<li>Don't use slurs.</li>
279-
</ul>
280-
346+
<h1>Social Comfort (More Ideas)</h1>
281347
</section>
282348
<section class="slide" id="social_comfort_pay_attention_to_pronouns">
283349
<h2>Social Comfort (pay attention to pronouns)</h2>
@@ -289,42 +355,6 @@ <h2>Social Comfort (pay attention to pronouns)</h2>
289355
<li>refrain from gender specific terms like "hey guys", "hello ladies"</li>
290356
</ul>
291357

292-
</section>
293-
<section class="slide" id="social_comfort_even_more_ideas">
294-
<h2>Social Comfort (Even More Ideas)</h2>
295-
296-
<h4>Represent the diverse and welcoming community we stand for</h4>
297-
298-
<ul>
299-
<li>Don't mock other languages or technologies.</li>
300-
<li>Leave your nerdy flame wars at the door.</li>
301-
<li>Windows is fine. PHP is fine. Javascript is fine.</li>
302-
<li>Be genuinely interested in people's experiences. ("You built something? That's cool. What does it do?")</li>
303-
<li>Appreciate that different technologies have different trade-offs. Being easily accessible is one of them.</li>
304-
</ul>
305-
306-
</section>
307-
<section class="slide" id="code_of_conduct_violations">
308-
<h2>Code of Conduct Violations</h2>
309-
310-
<p>The Berlin Code of Conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.</p>
311-
312-
<h4>Q: How do I react if an attendee complains about CoC violation?</h4>
313-
314-
<h4>A: Bring them to an orga-team member</h4>
315-
316-
</section>
317-
<section class="slide" id="discussion_technical_capability">
318-
<h2>Discussion: Technical Capability</h2>
319-
320-
<h3>How can you help people feel technically capable?</h3>
321-
322-
<h3>What kinds of insecurities might your student have?</h3>
323-
324-
<h3>How can you bolster their confidence?</h3>
325-
326-
<p>DISCUSS!</p>
327-
328358
</section>
329359
<section class="slide" id="technical_capability_ideas">
330360
<h2>Technical Capability (Ideas)</h2>
@@ -387,18 +417,6 @@ <h4>Find the right level</h4>
387417
</li>
388418
</ul>
389419

390-
</section>
391-
<section class="slide" id="discussion_do_you_know_whats_up">
392-
<h2>Discussion (Do you know what's up?)</h2>
393-
394-
<h4>How can you help people feel like you know what's going on?</h4>
395-
396-
<h4>What are things you can do to help the students trust you?</h4>
397-
398-
<h4>What are some things to avoid?</h4>
399-
400-
<p>DISCUSS!</p>
401-
402420
</section>
403421
<section class="slide" id="know_whats_up_ideas">
404422
<h2>Know What's Up (Ideas)</h2>
@@ -455,42 +473,23 @@ <h4>Pace yourself!</h4>
455473
</ul>
456474

457475
</section>
458-
<section class="slide" id="discussion_challenges">
459-
<h2>Discussion: Challenges</h2>
460-
461-
<p>Talk about what problems you might anticipate, and what to do about them.</p>
462-
463-
<h4>Some issues:</h4>
464-
465-
<ul>
466-
<li>Student is in the wrong class level</li>
467-
<li>Student is disruptive</li>
468-
<li>Student is disengaged</li>
469-
</ul>
470-
471-
<p>DISCUSS!</p>
472-
473-
</section>
474-
<section class="slide" id="discussion_coaching">
475-
<h2>Discussion: Coaching</h2>
476-
477-
<h4>What are the benefits of having two coaches in a group?</h4>
476+
<section class="slide" id="code_of_conduct_violations">
477+
<h2>Code of Conduct Violations</h2>
478478

479-
<h4>How can you divide the roles between the coaches?</h4>
479+
<p>The Berlin Code of Conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.</p>
480480

481-
<h4>How can you get a good dynamic between the whole team, both attendees and coaches?</h4>
481+
<h4>Q: How do I react if an attendee complains about CoC violation?</h4>
482482

483-
<p>DISCUSS!</p>
483+
<h4>A: Bring them to an orga-team member</h4>
484484

485485
</section>
486486
<section class="slide" id="coaching_build_a_team">
487487
<h2>Coaching: Build a Team</h2>
488488

489489
<ul>
490-
<li>ClojureBridge normally makes a distinction between coaches and TAs (teaching assistants).</li>
491490
<li>We will try to form groups with two coaches per group.</li>
492491
<li>You can decide on one coach to take the lead, or you can tag-team.</li>
493-
<li>There will also be some "floating" TAs that can go around and help.</li>
492+
<li>There will also be some "floating" coaches that can go around and help.</li>
494493
</ul>
495494

496495
</section>
@@ -514,16 +513,31 @@ <h4>Co-coaching (Some Ideas)</h4>
514513
</ul>
515514

516515
</section>
517-
<section class="slide" id="discussion_comprehension">
518-
<h2>Discussion: Comprehension</h2>
516+
<section class="slide" id="the_curriculum">
517+
<h2>The Curriculum</h2>
519518

520-
<h4>How can you tell if they understand the words you're saying?</h4>
519+
<ul>
520+
<li>Most people will go through the curriculum on our web page</li>
521+
</ul>
521522

522-
<h4>What are good questions to ask to check comprehension?</h4>
523+
<p><a href="http://clojurebridge-berlin.org/curriculum">http://clojurebridge-berlin.org/curriculum</a></p>
523524

524-
<h4>What did your favorite coaches do to gauge understanding?</h4>
525+
<h3>It's a slideshow that goes through the concepts of:</h3>
525526

526-
<p>DISCUSS!</p>
527+
<ul>
528+
<li>values</li>
529+
<li>data structures</li>
530+
<li>functions</li>
531+
<li>control logic</li>
532+
</ul>
533+
534+
<h2>Please take a look :)</h2>
535+
536+
</section>
537+
<section class="slide" id="some_people_are_trialing_a_new_curriculum">
538+
<h2>Some people are trialing a new Curriculum</h2>
539+
540+
<p>But everyone should still install NightCode for now</p>
527541

528542
</section>
529543
<section class="slide" id="practical_recap">
@@ -569,30 +583,33 @@ <h2>deck.rb presentation</h2>
569583
<li><a href="#whats_a_clojurebridge">What&#39;s a ClojureBridge?</a></li>
570584
<li><a href="#how_does_a_workshop_work">How does a workshop work?</a></li>
571585
<li><a href="#installfest">Installfest!</a></li>
586+
<li><a href="#on_that_note">On that note...</a></li>
587+
<li><a href="#try_to_suppress_your_understandable_culturallyinfluenced_sexism">Try to suppress your (understandable) culturally-influenced sexism</a></li>
572588
<li><a href="#typical_clojurebridge_schedule">Typical ClojureBridge Schedule</a></li>
573589
<li><a href="#is_clojurebridge_open_source">Is ClojureBridge Open Source?</a></li>
574590
<li><a href="#is_clojurebridge_open_source">Is ClojureBridge Open Source?</a></li>
575591
<li><a href="#discussion_topics">Discussion Topics</a></li>
576592
<li><a href="#how_to_make_your_class_awesome">How to make your class awesome</a></li>
577593
<li><a href="#discussion_social_comfort">Discussion: Social Comfort</a></li>
594+
<li><a href="#discussion_do_you_know_whats_up">Discussion (Do you know what&#39;s up?)</a></li>
595+
<li><a href="#discussion_technical_capability">Discussion: Technical Capability</a></li>
596+
<li><a href="#discussion_challenges">Discussion: Challenges</a></li>
597+
<li><a href="#discussion_coaching">Discussion: Coaching</a></li>
598+
<li><a href="#what_we_came_up_with">What we came up with</a></li>
578599
<li><a href="#social_comfort_ideas">Social Comfort (Ideas)</a></li>
579600
<li><a href="#social_comfort_more_ideas">Social Comfort (More Ideas)</a></li>
580601
<li><a href="#social_comfort_pay_attention_to_pronouns">Social Comfort (pay attention to pronouns)</a></li>
581-
<li><a href="#social_comfort_even_more_ideas">Social Comfort (Even More Ideas)</a></li>
582-
<li><a href="#code_of_conduct_violations">Code of Conduct Violations</a></li>
583-
<li><a href="#discussion_technical_capability">Discussion: Technical Capability</a></li>
584602
<li><a href="#technical_capability_ideas">Technical Capability (Ideas)</a></li>
585603
<li><a href="#technical_capability_more_ideas">Technical Capability (More Ideas)</a></li>
586604
<li><a href="#technical_capability_even_more_ideas">Technical Capability (Even More Ideas)</a></li>
587-
<li><a href="#discussion_do_you_know_whats_up">Discussion (Do you know what&#39;s up?)</a></li>
588605
<li><a href="#know_whats_up_ideas">Know What&#39;s Up (Ideas)</a></li>
589606
<li><a href="#know_whats_up_more_ideas">Know What&#39;s Up (More Ideas)</a></li>
590607
<li><a href="#know_whats_up_even_more_ideas">Know What&#39;s Up (Even More Ideas)</a></li>
591-
<li><a href="#discussion_challenges">Discussion: Challenges</a></li>
592-
<li><a href="#discussion_coaching">Discussion: Coaching</a></li>
608+
<li><a href="#code_of_conduct_violations">Code of Conduct Violations</a></li>
593609
<li><a href="#coaching_build_a_team">Coaching: Build a Team</a></li>
594610
<li><a href="#coaching_dynamics_ideas">Coaching Dynamics (Ideas)</a></li>
595-
<li><a href="#discussion_comprehension">Discussion: Comprehension</a></li>
611+
<li><a href="#the_curriculum">The Curriculum</a></li>
612+
<li><a href="#some_people_are_trialing_a_new_curriculum">Some people are trialing a new Curriculum</a></li>
596613
<li><a href="#practical_recap">Practical Recap</a></li>
597614
</ul>
598615
</div>

0 commit comments

Comments
 (0)