From ba448976c691a4a2719caefff31f51220558dcf7 Mon Sep 17 00:00:00 2001
From: Dave Liepmann <dave.liepmann@gmail.com>
Date: Fri, 4 Aug 2017 16:48:50 +0200
Subject: [PATCH 1/8] Fix "Code of Contact" typo. Fixes #63

---
 learners_group.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/learners_group.html b/learners_group.html
index cba2344..f4ec7a4 100644
--- a/learners_group.html
+++ b/learners_group.html
@@ -50,7 +50,7 @@ <h2>Clojure Dojo Learners Group</h2>
         <ul>
           <li>
             <p>Location: <a href="http://co-up.de/about.html" title="co-up about">co-up coworking space</a> 3rd floor <br>near U8/U1 Kottbusser Tor.<br>
-              <a href="http://co-up.de/code-of-conduct.html" title="co-up coc">Code of Contact</a>, <a href="http://co-up.de/space-instructions.html" title="co-up location">Location/ accessibility info</a></p>
+              <a href="http://co-up.de/code-of-conduct.html" title="co-up coc">Code of Conduct</a>, <a href="http://co-up.de/space-instructions.html" title="co-up location">Location/ accessibility info</a></p>
           </li>
           <li>
             <p>When: Every Wednesdays of every month except for the second Wednesday (that's when we go to the Clojure Meetup)</p>

From ed7684496330cec7b332da12bf5bbac23f64ecd7 Mon Sep 17 00:00:00 2001
From: Dave Liepmann <dave.liepmann@gmail.com>
Date: Fri, 4 Aug 2017 16:51:02 +0200
Subject: [PATCH 2/8] Update # of workshops we've had in Berlin. Fixes #62

---
 coaches_training.deck.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/coaches_training.deck.html b/coaches_training.deck.html
index 07dc689..50aa389 100644
--- a/coaches_training.deck.html
+++ b/coaches_training.deck.html
@@ -92,7 +92,7 @@ <h3>ClojureBridge</h3>
 <ul>
 <li>First workshop April 2014</li>
 <li>Since then over 40 workshops in the US, UK, Ireland, Australia, Scotland, Finland, Sweden, Brazil, Canada, and... Germany!</li>
-<li>So far two workshops in Berlin: July 2015, January 2016, and now the third one coming up! 🎉</li>
+<li>In Berlin we’ve had lots: July 2015, January 2016, June 2016, November 2016 (what a year!), and now planning for November 2017. 🎉</li>
 </ul>
 
 </section>
@@ -581,7 +581,7 @@ <h2>deck.rb presentation</h2>
 });
 // ]]>
     </script>
-    
+
 <!--Deck Core and extensions-->
 
     <script src="/deck.js/core/deck.core.js" type="text/javascript"></script>

From 93492fe081ff454a29c326840ec6ef06a1df207d Mon Sep 17 00:00:00 2001
From: Dave Liepmann <dave.liepmann@gmail.com>
Date: Fri, 4 Aug 2017 17:03:25 +0200
Subject: [PATCH 3/8] Add slide explaining Berlin Code of Conduct

---
 coaches_training.deck.html | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/coaches_training.deck.html b/coaches_training.deck.html
index 50aa389..959f038 100644
--- a/coaches_training.deck.html
+++ b/coaches_training.deck.html
@@ -44,7 +44,26 @@ <h3>Discussion is key!</h3>
 
 <h3>Don't let the presenter(s) do all the talking!</h3>
 
-</section>
+    </section>
+
+
+    <section class="slide" id="code_of_conduct">
+      <h2>Code of Conduct</h2>
+
+      <p><a href="berlincodeofconduct.org">berlincodeofconduct.org</a> 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>
+
+      <h3>Expected Behavior</h3>
+
+      <ul><li>Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.</li>
+        <li>Exercise consideration and respect in your speech and actions.</li>
+        <li>Attempt collaboration before conflict.</li>
+        <li>Refrain from demeaning, discriminatory, or harassing behavior and speech.</li>
+        <li>Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.</li>
+      </ul>
+
+    </section>
+
+
     <section class="slide" id="why_clojurebridge">
 <h2>Why ClojureBridge?</h2>
 

From 8856224e2f9991a45840962e28d1cf2fdd71d7a9 Mon Sep 17 00:00:00 2001
From: Dave Liepmann <dave.liepmann@gmail.com>
Date: Fri, 4 Aug 2017 17:04:06 +0200
Subject: [PATCH 4/8] Enforce indentation

---
 coaches_training.deck.html | 716 ++++++++++++++++++-------------------
 1 file changed, 358 insertions(+), 358 deletions(-)

diff --git a/coaches_training.deck.html b/coaches_training.deck.html
index 959f038..37d84f6 100644
--- a/coaches_training.deck.html
+++ b/coaches_training.deck.html
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+          "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
   <head><meta content="text/html;charset=UTF-8" http-equiv="content-type" />
     <title>deck.rb presentation</title>
@@ -21,28 +21,28 @@
   </head>
   <body class="deck-container">
     <section class="slide" id="clojurebridge_coaches_training">
-<h1>ClojureBridge Coaches Training</h1>
-</section>
+      <h1>ClojureBridge Coaches Training</h1>
+    </section>
     <section class="slide" id="todays_agenda">
-<h2>Today's Agenda</h2>
+      <h2>Today's Agenda</h2>
 
-<h3>Background and Practicalities</h3>
+      <h3>Background and Practicalities</h3>
 
-<h3>Discussion Topics &amp; Coaching Tips</h3>
+      <h3>Discussion Topics &amp; Coaching Tips</h3>
 
-</section>
+    </section>
     <section class="slide" id="what_is_this">
-<h2>What is this?</h2>
+      <h2>What is this?</h2>
 
-<p>You're probably at a coaches training for ClojureBridge.</p>
+      <p>You're probably at a coaches training for ClojureBridge.</p>
 
-<p>This slide deck is a tool to facilitate conversations about coaching best practices and challenges, specifically for ClojureBridge workshops.</p>
+      <p>This slide deck is a tool to facilitate conversations about coaching best practices and challenges, specifically for ClojureBridge workshops.</p>
 
-<p>It helps to have a whiteboard or those giant sticky notes for the discussions if possible.</p>
+      <p>It helps to have a whiteboard or those giant sticky notes for the discussions if possible.</p>
 
-<h3>Discussion is key!</h3>
+      <h3>Discussion is key!</h3>
 
-<h3>Don't let the presenter(s) do all the talking!</h3>
+      <h3>Don't let the presenter(s) do all the talking!</h3>
 
     </section>
 
@@ -65,484 +65,484 @@ <h3>Expected Behavior</h3>
 
 
     <section class="slide" id="why_clojurebridge">
-<h2>Why ClojureBridge?</h2>
+      <h2>Why ClojureBridge?</h2>
 
-<p>We're making tech more diverse and more welcoming!</p>
+      <p>We're making tech more diverse and more welcoming!</p>
 
-<h3>How?</h3>
+      <h3>How?</h3>
 
-<ul>
-<li>We throw super-welcoming, fun, free workshops.</li>
-<li>We provide great networking opportunities for students and volunteers.</li>
-<li>We help our volunteers become more empathatic and better communicators.</li>
-</ul>
+      <ul>
+        <li>We throw super-welcoming, fun, free workshops.</li>
+        <li>We provide great networking opportunities for students and volunteers.</li>
+        <li>We help our volunteers become more empathatic and better communicators.</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="introductions">
-<h2>Introductions</h2>
+      <h2>Introductions</h2>
 
-<h3>Who are you?</h3>
+      <h3>Who are you?</h3>
 
-<ul>
-<li>What's your name?</li>
-<li>What are your pronouns?</li>
-<li>Have you been to a ClojureBridge or similar workshops before? How many?</li>
-<li>What's your favorite place in Berlin?</li>
-<li>What's the most non-coding thing you do?</li>
-</ul>
+      <ul>
+        <li>What's your name?</li>
+        <li>What are your pronouns?</li>
+        <li>Have you been to a ClojureBridge or similar workshops before? How many?</li>
+        <li>What's your favorite place in Berlin?</li>
+        <li>What's the most non-coding thing you do?</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="whats_a_clojurebridge">
-<h2>What's a ClojureBridge?</h2>
+      <h2>What's a ClojureBridge?</h2>
 
-<p>Raise your hand if you've been to a workshop before!</p>
+      <p>Raise your hand if you've been to a workshop before!</p>
 
-<h3>RailsBridge Fun Facts</h3>
+      <h3>RailsBridge Fun Facts</h3>
 
-<ul>
-<li>Founded in 2009</li>
-<li>Its goal: make the community more diverse and more welcoming to newcomers.</li>
-<li>Since 2012 backed by Bridge Foundry,</li>
-<li>Also does MobileBridge, ng-bridge, Teaching Kids, and ... ClojureBridge!</li>
-</ul>
+      <ul>
+        <li>Founded in 2009</li>
+        <li>Its goal: make the community more diverse and more welcoming to newcomers.</li>
+        <li>Since 2012 backed by Bridge Foundry,</li>
+        <li>Also does MobileBridge, ng-bridge, Teaching Kids, and ... ClojureBridge!</li>
+      </ul>
 
-<h3>ClojureBridge</h3>
+      <h3>ClojureBridge</h3>
 
-<ul>
-<li>First workshop April 2014</li>
-<li>Since then over 40 workshops in the US, UK, Ireland, Australia, Scotland, Finland, Sweden, Brazil, Canada, and... Germany!</li>
-<li>In Berlin we’ve had lots: July 2015, January 2016, June 2016, November 2016 (what a year!), and now planning for November 2017. 🎉</li>
-</ul>
+      <ul>
+        <li>First workshop April 2014</li>
+        <li>Since then over 40 workshops in the US, UK, Ireland, Australia, Scotland, Finland, Sweden, Brazil, Canada, and... Germany!</li>
+        <li>In Berlin we’ve had lots: July 2015, January 2016, June 2016, November 2016 (what a year!), and now planning for November 2017. 🎉</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="how_does_a_workshop_work">
-<h2>How does a workshop work?</h2>
+      <h2>How does a workshop work?</h2>
 
-<p>On Friday, we get all the necessary technologies onto the students' computers (the Installfest).</p>
+      <p>On Friday, we get all the necessary technologies onto the students' computers (the Installfest).</p>
 
-<p>The next day we start with a general introduction, then break into small groups and work through the curriculum, with some talks and breaks in between.</p>
+      <p>The next day we start with a general introduction, then break into small groups and work through the curriculum, with some talks and breaks in between.</p>
 
-<p>In groups of 3 to 4 students and two coaches we work through the curriculum (a tutorial of Clojure) and then work on a Quil app (graphics library).
-Floating coaches are available for extra support.</p>
+      <p>In groups of 3 to 4 students and two coaches we work through the curriculum (a tutorial of Clojure) and then work on a Quil app (graphics library).
+        Floating coaches are available for extra support.</p>
 
-<p>You get as far as you get, don't rush to "finish" things.</p>
+      <p>You get as far as you get, don't rush to "finish" things.</p>
 
-</section>
+    </section>
     <section class="slide" id="installfest">
-<h2>Installfest!</h2>
+      <h2>Installfest!</h2>
 
-<p>We use NightCode as editor. Of course if people have their own preference then that's fine.</p>
+      <p>We use NightCode as editor. Of course if people have their own preference then that's fine.</p>
 
-<p>NightCode is pretty easy to install, it's just an executable JAR. We'll have a couple thumb drives to go around.</p>
+      <p>NightCode is pretty easy to install, it's just an executable JAR. We'll have a couple thumb drives to go around.</p>
 
-<p>Actually create and run a Quil project, so all dependencies are downloaded and available.</p>
+      <p>Actually create and run a Quil project, so all dependencies are downloaded and available.</p>
 
-<h4>Keep in mind:</h4>
+      <h4>Keep in mind:</h4>
 
-<ul>
-<li>There will be people with <em>all</em> kinds of computers.</li>
-<li>Even though Windows might not be your preferred development environment, we're here to encourage people and meet them wherever they are right now.</li>
-<li>Do NOT say bad things about Windows, even if it's frustrating.</li>
-<li>If you're not sure about something, grab another volunteer.</li>
-</ul>
+      <ul>
+        <li>There will be people with <em>all</em> kinds of computers.</li>
+        <li>Even though Windows might not be your preferred development environment, we're here to encourage people and meet them wherever they are right now.</li>
+        <li>Do NOT say bad things about Windows, even if it's frustrating.</li>
+        <li>If you're not sure about something, grab another volunteer.</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="typical_clojurebridge_schedule">
-<h2>Typical ClojureBridge Schedule</h2>
-
-<ul>
-<li><p>Friday, 6-10pm-ish: <strong>Installfest</strong> <br>get set up, meet the fellow attendees, with some nice food and drinks</p></li>
-<li>
-<p>Saturday's schedule</p>
-
-<ul>
-<li>9-9:30am: Check-in, coffee, small breakfast</li>
-<li>9:30-10am: Opening presentation</li>
-<li>10am-12:30pm: Class!</li>
-<li>12:30-1:30pm: Lunch &amp; lightning talks</li>
-<li>1:30pm-4:30pm: Class! (with a break sometime mid-afternoon)</li>
-<li>4:30-5:00pm: Closing presentation &amp; retros</li>
-<li>5:00pm-...: Free to hang around and socialize</li>
-</ul>
-</li>
-</ul>
-
-</section>
+      <h2>Typical ClojureBridge Schedule</h2>
+
+      <ul>
+        <li><p>Friday, 6-10pm-ish: <strong>Installfest</strong> <br>get set up, meet the fellow attendees, with some nice food and drinks</p></li>
+        <li>
+          <p>Saturday's schedule</p>
+
+          <ul>
+            <li>9-9:30am: Check-in, coffee, small breakfast</li>
+            <li>9:30-10am: Opening presentation</li>
+            <li>10am-12:30pm: Class!</li>
+            <li>12:30-1:30pm: Lunch &amp; lightning talks</li>
+            <li>1:30pm-4:30pm: Class! (with a break sometime mid-afternoon)</li>
+            <li>4:30-5:00pm: Closing presentation &amp; retros</li>
+            <li>5:00pm-...: Free to hang around and socialize</li>
+          </ul>
+        </li>
+      </ul>
+
+    </section>
     <section class="slide" id="is_clojurebridge_open_source">
-<h2>Is ClojureBridge Open Source?</h2>
+      <h2>Is ClojureBridge Open Source?</h2>
 
-<h3>WHY YES, THANK YOU FOR ASKING!</h3>
+      <h3>WHY YES, THANK YOU FOR ASKING!</h3>
 
-<h3>CLOJUREBRIDGE IS VERY OPEN SOURCE!</h3>
+      <h3>CLOJUREBRIDGE IS VERY OPEN SOURCE!</h3>
 
-<p>All the materials you're using were created by volunteers, and are on GitHub for forking and editing and using!</p>
+      <p>All the materials you're using were created by volunteers, and are on GitHub for forking and editing and using!</p>
 
-<p>If you see something that could be better, make a pull request. Pull requests are the lifeblood of ClojureBridge.</p>
+      <p>If you see something that could be better, make a pull request. Pull requests are the lifeblood of ClojureBridge.</p>
 
-<p>If you don't know how to make one, we'll help!</p>
+      <p>If you don't know how to make one, we'll help!</p>
 
-</section>
+    </section>
     <section class="slide" id="is_clojurebridge_open_source">
-<h2>Is ClojureBridge Open Source?</h2>
+      <h2>Is ClojureBridge Open Source?</h2>
 
-<h3>Curriculum</h3>
+      <h3>Curriculum</h3>
 
-<ul>
-<li><a href="https://github.com/clojurebridge/curriculum">Github: clojurebridge/curriculum</a></li>
-<li><a href="https://github.com/clojurebridge-berlin/curriculum">Gituhb: clojurebridge-berlin/curriculum</a></li>
-<li><a href="https://groups.google.com/forum/#!forum/clojurebridge-curriculum">Google Groups — clojurebridge-curriculum</a></li>
-</ul>
+      <ul>
+        <li><a href="https://github.com/clojurebridge/curriculum">Github: clojurebridge/curriculum</a></li>
+        <li><a href="https://github.com/clojurebridge-berlin/curriculum">Gituhb: clojurebridge-berlin/curriculum</a></li>
+        <li><a href="https://groups.google.com/forum/#!forum/clojurebridge-curriculum">Google Groups — clojurebridge-curriculum</a></li>
+      </ul>
 
-<h3>Our Site</h3>
+      <h3>Our Site</h3>
 
-<ul>
-<li><a href="https://github.com/clojurebridge-berlin/clojurebridge-berlin.github.io">Github: clojurebridge-berlin/clojurebridge-berlin.github.io</a></li>
-</ul>
+      <ul>
+        <li><a href="https://github.com/clojurebridge-berlin/clojurebridge-berlin.github.io">Github: clojurebridge-berlin/clojurebridge-berlin.github.io</a></li>
+      </ul>
 
-<h3>Our Wiki</h3>
+      <h3>Our Wiki</h3>
 
-<ul>
-<li><a href="https://github.com/clojurebridge-berlin/organization/wiki">https://github.com/clojurebridge-berlin/organization/wiki</a></li>
-</ul>
+      <ul>
+        <li><a href="https://github.com/clojurebridge-berlin/organization/wiki">https://github.com/clojurebridge-berlin/organization/wiki</a></li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="discussion_topics">
-<h1>Discussion Topics</h1>
-</section>
+      <h1>Discussion Topics</h1>
+    </section>
     <section class="slide" id="how_to_make_your_class_awesome">
-<h2>How to make your class awesome</h2>
+      <h2>How to make your class awesome</h2>
 
-<p>How to make your class awesome? We created some arbitrary categories for discussion. We'll go through each one, and get input from the group (whiteboard \o/), and then provide some additional ideas and suggestions.</p>
+      <p>How to make your class awesome? We created some arbitrary categories for discussion. We'll go through each one, and get input from the group (whiteboard \o/), and then provide some additional ideas and suggestions.</p>
 
-<h3>Social Comfort</h3>
+      <h3>Social Comfort</h3>
 
-<h3>Technical Capability</h3>
+      <h3>Technical Capability</h3>
 
-<h3>Do you know what's up?</h3>
+      <h3>Do you know what's up?</h3>
 
-<h3>Challenges</h3>
+      <h3>Challenges</h3>
 
-<h3>Coaching</h3>
+      <h3>Coaching</h3>
 
-<h3>Comprehension</h3>
+      <h3>Comprehension</h3>
 
-</section>
+    </section>
     <section class="slide" id="discussion_social_comfort">
-<h2>Discussion: Social Comfort</h2>
+      <h2>Discussion: Social Comfort</h2>
 
-<h4>Imagine:</h4>
+      <h4>Imagine:</h4>
 
-<ul>
-<li>You're trying to do something difficult</li>
-<li>You're in a group of strangers, many of whom know how to do it better than you</li>
-<li>You've tried before but got lost or bored or confused</li>
-<li>You don't feel like you can articulate your thoughts and questions</li>
-<li>You don't know the right names for anything</li>
-</ul>
+      <ul>
+        <li>You're trying to do something difficult</li>
+        <li>You're in a group of strangers, many of whom know how to do it better than you</li>
+        <li>You've tried before but got lost or bored or confused</li>
+        <li>You don't feel like you can articulate your thoughts and questions</li>
+        <li>You don't know the right names for anything</li>
+      </ul>
 
-<h4>When was the last time you felt this way?</h4>
+      <h4>When was the last time you felt this way?</h4>
 
-<h4>How can we help make this easier?</h4>
+      <h4>How can we help make this easier?</h4>
 
-<h4>How can you help people feel socially comfortable?</h4>
+      <h4>How can you help people feel socially comfortable?</h4>
 
-<p>DISCUSS!</p>
+      <p>DISCUSS!</p>
 
-</section>
+    </section>
     <section class="slide" id="social_comfort_ideas">
-<h2>Social Comfort (Ideas)</h2>
+      <h2>Social Comfort (Ideas)</h2>
 
-<h4>Introductions</h4>
+      <h4>Introductions</h4>
 
-<ul>
-<li>Include name, profession, why are you here / goals for today's class, and something silly.</li>
-<li>Don't rush, even if you have a big class.</li>
-<li>If someone joins the class late, ask them to introduce themselves.</li>
-</ul>
+      <ul>
+        <li>Include name, profession, why are you here / goals for today's class, and something silly.</li>
+        <li>Don't rush, even if you have a big class.</li>
+        <li>If someone joins the class late, ask them to introduce themselves.</li>
+      </ul>
 
-<h4>Icebreakers</h4>
+      <h4>Icebreakers</h4>
 
-<ul>
-<li>Name games! Admit up front that most people are bad at learning new names.</li>
-<li>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.</li>
-</ul>
+      <ul>
+        <li>Name games! Admit up front that most people are bad at learning new names.</li>
+        <li>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.</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="social_comfort_more_ideas">
-<h2>Social Comfort (More Ideas)</h2>
+      <h2>Social Comfort (More Ideas)</h2>
 
-<h4>Try to suppress your (understandable) culturally-influenced sexism</h4>
+      <h4>Try to suppress your (understandable) culturally-influenced sexism</h4>
 
-<ul>
-<li>Don't hit on people. No sexual advances. None. Even at the after-party.</li>
-<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>
-<li>Don't make gender-based generalizations ("Women are better at X, because ...")</li>
-<li>Don't make references to people's bodies or state your opinion of them.</li>
-<li>Don't use slurs.</li>
-</ul>
+      <ul>
+        <li>Don't hit on people. No sexual advances. None. Even at the after-party.</li>
+        <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>
+        <li>Don't make gender-based generalizations ("Women are better at X, because ...")</li>
+        <li>Don't make references to people's bodies or state your opinion of them.</li>
+        <li>Don't use slurs.</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="social_comfort_pay_attention_to_pronouns">
-<h2>Social Comfort (pay attention to pronouns)</h2>
+      <h2>Social Comfort (pay attention to pronouns)</h2>
 
-<ul>
-<li>attendees are women and non-binary people</li>
-<li>attendees are asked to write down their pronouns on their name tags</li>
-<li>please don't assume anybody's gender</li>
-<li>refrain from gender specific terms like "hey guys", "hello ladies"</li>
-</ul>
+      <ul>
+        <li>attendees are women and non-binary people</li>
+        <li>attendees are asked to write down their pronouns on their name tags</li>
+        <li>please don't assume anybody's gender</li>
+        <li>refrain from gender specific terms like "hey guys", "hello ladies"</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="social_comfort_even_more_ideas">
-<h2>Social Comfort (Even More Ideas)</h2>
+      <h2>Social Comfort (Even More Ideas)</h2>
 
-<h4>Represent the diverse and welcoming community we stand for</h4>
+      <h4>Represent the diverse and welcoming community we stand for</h4>
 
-<ul>
-<li>Don't mock other languages or technologies.</li>
-<li>Leave your nerdy flame wars at the door.</li>
-<li>Windows is fine. PHP is fine. Javascript is fine.</li>
-<li>Be genuinely interested in people's experiences. ("You built something? That's cool. What does it do?")</li>
-<li>Appreciate that different technologies have different trade-offs. Being easily accessible is one of them.</li>
-</ul>
+      <ul>
+        <li>Don't mock other languages or technologies.</li>
+        <li>Leave your nerdy flame wars at the door.</li>
+        <li>Windows is fine. PHP is fine. Javascript is fine.</li>
+        <li>Be genuinely interested in people's experiences. ("You built something? That's cool. What does it do?")</li>
+        <li>Appreciate that different technologies have different trade-offs. Being easily accessible is one of them.</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="discussion_technical_capability">
-<h2>Discussion: Technical Capability</h2>
+      <h2>Discussion: Technical Capability</h2>
 
-<h3>How can you help people feel technically capable?</h3>
+      <h3>How can you help people feel technically capable?</h3>
 
-<h3>What kinds of insecurities might your student have?</h3>
+      <h3>What kinds of insecurities might your student have?</h3>
 
-<h3>How can you bolster their confidence?</h3>
+      <h3>How can you bolster their confidence?</h3>
 
-<p>DISCUSS!</p>
+      <p>DISCUSS!</p>
 
-</section>
+    </section>
     <section class="slide" id="technical_capability_ideas">
-<h2>Technical Capability (Ideas)</h2>
+      <h2>Technical Capability (Ideas)</h2>
 
-<h4>Being confused is normal</h4>
+      <h4>Being confused is normal</h4>
 
-<ul>
-<li>Not knowing stuff is normal, even the pros spend half their day googling</li>
-<li>If you keep at it it gets better, more quickly than you think</li>
-<li>No need to make things perfect. Just build stuff, have fun!</li>
-<li>Mistakes == Learning!</li>
-</ul>
+      <ul>
+        <li>Not knowing stuff is normal, even the pros spend half their day googling</li>
+        <li>If you keep at it it gets better, more quickly than you think</li>
+        <li>No need to make things perfect. Just build stuff, have fun!</li>
+        <li>Mistakes == Learning!</li>
+      </ul>
 
-<h4>Define technical concepts</h4>
+      <h4>Define technical concepts</h4>
 
-<ul>
-<li>Define technical terms! Several times!</li>
-<li>Assume anyone you're coaching has zero knowledge but infinite intelligence.</li>
-<li>Remember people's backgrounds (Javascript, Ruby, Java, HTML/CSS,) and relate where possible.</li>
-<li>Don't be afraid to use metaphors. If they are a cook, try a cooking analogy.</li>
-</ul>
+      <ul>
+        <li>Define technical terms! Several times!</li>
+        <li>Assume anyone you're coaching has zero knowledge but infinite intelligence.</li>
+        <li>Remember people's backgrounds (Javascript, Ruby, Java, HTML/CSS,) and relate where possible.</li>
+        <li>Don't be afraid to use metaphors. If they are a cook, try a cooking analogy.</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="technical_capability_more_ideas">
-<h2>Technical Capability (More Ideas)</h2>
+      <h2>Technical Capability (More Ideas)</h2>
 
-<h4>Encourage collaboration and interaction</h4>
+      <h4>Encourage collaboration and interaction</h4>
 
-<ul>
-<li>Explicitly encourage students to try to answer each other's questions.</li>
-<li>If a question is asked, ask if anyone in the class thinks they can explain.</li>
-<li>Be especially encouraging of the first few questions, to try to get things rolling.</li>
-<li>Good responses to questions: "I'm glad you asked!" or "I actually wondered that, too." or "Great question!"</li>
-</ul>
+      <ul>
+        <li>Explicitly encourage students to try to answer each other's questions.</li>
+        <li>If a question is asked, ask if anyone in the class thinks they can explain.</li>
+        <li>Be especially encouraging of the first few questions, to try to get things rolling.</li>
+        <li>Good responses to questions: "I'm glad you asked!" or "I actually wondered that, too." or "Great question!"</li>
+      </ul>
 
-<h4>Be Super Positive, Always</h4>
+      <h4>Be Super Positive, Always</h4>
 
-<ul>
-<li>Students have diverse backgrounds. Appreciate this fact.</li>
-<li>If they aren't getting a concept, avoid anything that might shame them.</li>
-<li>Don't be surprised when someone hasn't heard of something before.</li>
-<li>Don't grab anyone's keyboard. Avoid taking over unless you think it's <em>really</em> necessary. Ask before you do. "Mind if I drive for a sec?" But really, don't.</li>
-</ul>
+      <ul>
+        <li>Students have diverse backgrounds. Appreciate this fact.</li>
+        <li>If they aren't getting a concept, avoid anything that might shame them.</li>
+        <li>Don't be surprised when someone hasn't heard of something before.</li>
+        <li>Don't grab anyone's keyboard. Avoid taking over unless you think it's <em>really</em> necessary. Ask before you do. "Mind if I drive for a sec?" But really, don't.</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="technical_capability_even_more_ideas">
-<h2>Technical Capability (Even More Ideas)</h2>
+      <h2>Technical Capability (Even More Ideas)</h2>
 
-<h4>Find the right level</h4>
+      <h4>Find the right level</h4>
 
-<ul>
-<li>Don't go too deep for your class level, but also, don't gloss over things.</li>
-<li>When trying to be accurate, it's easy to go down a rabbit hole of specificity. Avoid.</li>
-<li>Work with the co-coaches to make sure no one goes down that rabbit hole. Accountability!</li>
-<li>Explain the big picture of a command <em>before</em> they type it in.
+      <ul>
+        <li>Don't go too deep for your class level, but also, don't gloss over things.</li>
+        <li>When trying to be accurate, it's easy to go down a rabbit hole of specificity. Avoid.</li>
+        <li>Work with the co-coaches to make sure no one goes down that rabbit hole. Accountability!</li>
+        <li>Explain the big picture of a command <em>before</em> they type it in.
 
-<ul>
-<li>i.e., before typing the command to deploy to Heroku, explain the difference between localhost and Heroku.</li>
-</ul>
-</li>
-</ul>
+          <ul>
+            <li>i.e., before typing the command to deploy to Heroku, explain the difference between localhost and Heroku.</li>
+          </ul>
+        </li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="discussion_do_you_know_whats_up">
-<h2>Discussion (Do you know what's up?)</h2>
+      <h2>Discussion (Do you know what's up?)</h2>
 
-<h4>How can you help people feel like you know what's going on?</h4>
+      <h4>How can you help people feel like you know what's going on?</h4>
 
-<h4>What are things you can do to help the students trust you?</h4>
+      <h4>What are things you can do to help the students trust you?</h4>
 
-<h4>What are some things to avoid?</h4>
+      <h4>What are some things to avoid?</h4>
 
-<p>DISCUSS!</p>
+      <p>DISCUSS!</p>
 
-</section>
+    </section>
     <section class="slide" id="know_whats_up_ideas">
-<h2>Know What's Up (Ideas)</h2>
+      <h2>Know What's Up (Ideas)</h2>
 
-<h4>Know what's going on</h4>
+      <h4>Know what's going on</h4>
 
-<ul>
-<li>Mention planned breaks, lunch time</li>
-<li>Remind students that there is a closing presentation at the end</li>
-<li>Make sure they know where the bathroom is</li>
-<li>Let them know they can hang around and socialize afterwards</li>
-</ul>
+      <ul>
+        <li>Mention planned breaks, lunch time</li>
+        <li>Remind students that there is a closing presentation at the end</li>
+        <li>Make sure they know where the bathroom is</li>
+        <li>Let them know they can hang around and socialize afterwards</li>
+      </ul>
 
-<h4>Establish a few ground rules</h4>
+      <h4>Establish a few ground rules</h4>
 
-<ul>
-<li>Questions are always welcome, even if the student thinks it might be dumb. "That's a <strong>GREAT</strong> question"</li>
-<li>Explain that if someone has trouble, the coaches will help troubleshoot.</li>
-<li>If anyone wants to switch classes, tell them they should feel TOTALLY COMFORTABLE switching at any point.</li>
-<li>Have breaks! Eat a muffin! Have a look at what other groups are doing!</li>
-</ul>
+      <ul>
+        <li>Questions are always welcome, even if the student thinks it might be dumb. "That's a <strong>GREAT</strong> question"</li>
+        <li>Explain that if someone has trouble, the coaches will help troubleshoot.</li>
+        <li>If anyone wants to switch classes, tell them they should feel TOTALLY COMFORTABLE switching at any point.</li>
+        <li>Have breaks! Eat a muffin! Have a look at what other groups are doing!</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="know_whats_up_more_ideas">
-<h2>Know What's Up (More Ideas)</h2>
-
-<h4>Teaching style</h4>
-
-<ul>
-<li>Know people's name, and use it</li>
-<li>You can correct people in a nice and encouraging way
-
-<ul>
-<li>"Well, this might work better and this is why."</li>
-<li>"Can you explain how you came to that conclusion?"</li>
-<li>"Does anyone have a different answer?"</li>
-<li>"Ah, I see what you're trying to do."</li>
-</ul>
-</li>
-<li>Ask yourself questions and answer them.</li>
-</ul>
+      <h2>Know What's Up (More Ideas)</h2>
+
+      <h4>Teaching style</h4>
+
+      <ul>
+        <li>Know people's name, and use it</li>
+        <li>You can correct people in a nice and encouraging way
+
+          <ul>
+            <li>"Well, this might work better and this is why."</li>
+            <li>"Can you explain how you came to that conclusion?"</li>
+            <li>"Does anyone have a different answer?"</li>
+            <li>"Ah, I see what you're trying to do."</li>
+          </ul>
+        </li>
+        <li>Ask yourself questions and answer them.</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="know_whats_up_even_more_ideas">
-<h2>Know What's Up (Even More Ideas)</h2>
+      <h2>Know What's Up (Even More Ideas)</h2>
 
-<h4>Pace yourself!</h4>
+      <h4>Pace yourself!</h4>
 
-<ul>
-<li>Don't go too fast. You will probably go too fast. Check in occasionally to ensure everyone is still with you.</li>
-<li>You can say the same thing THREE TIMES and it will not be boring yet.</li>
-<li>When you ask a question, wait TEN WHOLE SECONDS before saying anything else. People need time to think.</li>
-<li>Don't let the most advanced students dictate the pacing or answer all the questions.</li>
-</ul>
+      <ul>
+        <li>Don't go too fast. You will probably go too fast. Check in occasionally to ensure everyone is still with you.</li>
+        <li>You can say the same thing THREE TIMES and it will not be boring yet.</li>
+        <li>When you ask a question, wait TEN WHOLE SECONDS before saying anything else. People need time to think.</li>
+        <li>Don't let the most advanced students dictate the pacing or answer all the questions.</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="discussion_challenges">
-<h2>Discussion: Challenges</h2>
+      <h2>Discussion: Challenges</h2>
 
-<p>Talk about what problems you might anticipate, and what to do about them.</p>
+      <p>Talk about what problems you might anticipate, and what to do about them.</p>
 
-<h4>Some issues:</h4>
+      <h4>Some issues:</h4>
 
-<ul>
-<li>Student is in the wrong class level</li>
-<li>Student is disruptive</li>
-<li>Student is disengaged</li>
-</ul>
+      <ul>
+        <li>Student is in the wrong class level</li>
+        <li>Student is disruptive</li>
+        <li>Student is disengaged</li>
+      </ul>
 
-<p>DISCUSS!</p>
+      <p>DISCUSS!</p>
 
-</section>
+    </section>
     <section class="slide" id="discussion_coaching">
-<h2>Discussion: Coaching</h2>
+      <h2>Discussion: Coaching</h2>
 
-<h4>What are the benefits of having two coaches in a group?</h4>
+      <h4>What are the benefits of having two coaches in a group?</h4>
 
-<h4>How can you divide the roles between the coaches?</h4>
+      <h4>How can you divide the roles between the coaches?</h4>
 
-<h4>How can you get a good dynamic between the whole team, both attendees and coaches?</h4>
+      <h4>How can you get a good dynamic between the whole team, both attendees and coaches?</h4>
 
-<p>DISCUSS!</p>
+      <p>DISCUSS!</p>
 
-</section>
+    </section>
     <section class="slide" id="coaching_build_a_team">
-<h2>Coaching: Build a Team</h2>
+      <h2>Coaching: Build a Team</h2>
 
-<ul>
-<li>ClojureBridge normally makes a distinction between coaches and TAs (teaching assistants).</li>
-<li>We will try to form groups with two coaches per group.</li>
-<li>You can decide on one coach to take the lead, or you can tag-team.</li>
-<li>There will also be some "floating" TAs that can go around and help.</li>
-</ul>
+      <ul>
+        <li>ClojureBridge normally makes a distinction between coaches and TAs (teaching assistants).</li>
+        <li>We will try to form groups with two coaches per group.</li>
+        <li>You can decide on one coach to take the lead, or you can tag-team.</li>
+        <li>There will also be some "floating" TAs that can go around and help.</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="coaching_dynamics_ideas">
-<h2>Coaching Dynamics (Ideas)</h2>
+      <h2>Coaching Dynamics (Ideas)</h2>
 
-<ul>
-<li>Talk with your co-coach beforehand to set expectations</li>
-<li>It can make sense to have one person take the lead</li>
-<li>The other coach can give more individual assistance</li>
-<li>Swap these roles around if it makes sense. Find a healthy dynamic!</li>
-</ul>
+      <ul>
+        <li>Talk with your co-coach beforehand to set expectations</li>
+        <li>It can make sense to have one person take the lead</li>
+        <li>The other coach can give more individual assistance</li>
+        <li>Swap these roles around if it makes sense. Find a healthy dynamic!</li>
+      </ul>
 
-<h4>Co-coaching (Some Ideas)</h4>
+      <h4>Co-coaching (Some Ideas)</h4>
 
-<ul>
-<li>Both coaches can ask questions to encourage students to speak up.</li>
-<li>Ask your co-coach to explain a concept; they may be more technically advanced than you!</li>
-<li>Co-coaches can help people who get lost.</li>
-<li>If someone falls behind, the co-coach can take them aside to do some 1-on-1.</li>
-</ul>
+      <ul>
+        <li>Both coaches can ask questions to encourage students to speak up.</li>
+        <li>Ask your co-coach to explain a concept; they may be more technically advanced than you!</li>
+        <li>Co-coaches can help people who get lost.</li>
+        <li>If someone falls behind, the co-coach can take them aside to do some 1-on-1.</li>
+      </ul>
 
-</section>
+    </section>
     <section class="slide" id="discussion_comprehension">
-<h2>Discussion: Comprehension</h2>
+      <h2>Discussion: Comprehension</h2>
 
-<h4>How can you tell if they understand the words you're saying?</h4>
+      <h4>How can you tell if they understand the words you're saying?</h4>
 
-<h4>What are good questions to ask to check comprehension?</h4>
+      <h4>What are good questions to ask to check comprehension?</h4>
 
-<h4>What did your favorite coaches do to gauge understanding?</h4>
+      <h4>What did your favorite coaches do to gauge understanding?</h4>
 
-<p>DISCUSS!</p>
+      <p>DISCUSS!</p>
 
-</section>
+    </section>
     <section class="slide" id="practical_recap">
-<h2>Practical Recap</h2>
+      <h2>Practical Recap</h2>
 
-<p>Installfest: Friday <strong>25 November, 18:00</strong></p>
+      <p>Installfest: Friday <strong>25 November, 18:00</strong></p>
 
-<p>Workshop: Saturday <strong>26 November</strong>, doors open at <strong>9:00</strong>, starts at 9:30</p>
+      <p>Workshop: Saturday <strong>26 November</strong>, doors open at <strong>9:00</strong>, starts at 9:30</p>
 
-<p>Afterparty: at Volksbar</p>
+      <p>Afterparty: at Volksbar</p>
 
-<p> </p>
+      <p> </p>
 
-<p>Location: <strong>Wunderlist office (Microsoft)</strong></p>
+      <p>Location: <strong>Wunderlist office (Microsoft)</strong></p>
 
-<p>Karl-Liebknecht-Straße 32</p>
+      <p>Karl-Liebknecht-Straße 32</p>
 
-<p>Around the corner from <strong>Alexanderplatz</strong>.</p>
+      <p>Around the corner from <strong>Alexanderplatz</strong>.</p>
 
-<p> </p>
+      <p> </p>
 
-<p>Don't forget: laptop, powercord</p>
+      <p>Don't forget: laptop, powercord</p>
 
-<p>Go through the curriculum at home.</p>
+      <p>Go through the curriculum at home.</p>
 
-</section>
+    </section>
     <a class="deck-prev-link" href="#" title="Previous"></a><a class="deck-next-link" href="#" title="Next"></a>    <div class="slide_toc">      <div class="toggle">[contents]</div>
       <div class="table">
         <h2>deck.rb presentation</h2>
@@ -586,30 +586,30 @@ <h2>deck.rb presentation</h2>
     <form action="." class="goto-form" method="get"><label for="goto-slide">Go to slide:</label><input id="goto-slide" list="goto-datalist" name="slidenum" type="text" />
       <datalist id="goto-datalist"></datalist>
       <input type="submit" value="Go" /></form>
-    <a class="deck-permalink" href="." title="Permalink to this slide">#</a>
-    <script src="/deck.js/modernizr.custom.js"></script>
-    <script src="/deck.js/jquery-1.7.2.min.js"></script>
-    <script type="text/javascript">
-// <![CDATA[
-
-jQuery(document).ready(function($){
-    $('.slide_toc .toggle').click(function(){
-      $('.slide_toc .table').toggle();
-    });
-
-});
-// ]]>
-    </script>
-
-<!--Deck Core and extensions-->
-
-    <script src="/deck.js/core/deck.core.js" type="text/javascript"></script>
-    <script src="/deck.js/extensions/goto/deck.goto.js" type="text/javascript"></script>
-    <script src="/deck.js/extensions/menu/deck.menu.js" type="text/javascript"></script>
-    <script src="/deck.js/extensions/navigation/deck.navigation.js" type="text/javascript"></script>
-    <script src="/deck.js/extensions/status/deck.status.js" type="text/javascript"></script>
-    <script src="/deck.js/extensions/hash/deck.hash.js" type="text/javascript"></script>
-    <script src="/deck.js/extensions/scale/deck.scale.js" type="text/javascript"></script>
-    <script>$(function(){$.deck('.slide');});</script>
+      <a class="deck-permalink" href="." title="Permalink to this slide">#</a>
+      <script src="/deck.js/modernizr.custom.js"></script>
+      <script src="/deck.js/jquery-1.7.2.min.js"></script>
+      <script type="text/javascript">
+       // <![CDATA[
+
+       jQuery(document).ready(function($){
+           $('.slide_toc .toggle').click(function(){
+               $('.slide_toc .table').toggle();
+           });
+
+       });
+       // ]]>
+      </script>
+
+      <!--Deck Core and extensions-->
+
+      <script src="/deck.js/core/deck.core.js" type="text/javascript"></script>
+      <script src="/deck.js/extensions/goto/deck.goto.js" type="text/javascript"></script>
+      <script src="/deck.js/extensions/menu/deck.menu.js" type="text/javascript"></script>
+      <script src="/deck.js/extensions/navigation/deck.navigation.js" type="text/javascript"></script>
+      <script src="/deck.js/extensions/status/deck.status.js" type="text/javascript"></script>
+      <script src="/deck.js/extensions/hash/deck.hash.js" type="text/javascript"></script>
+      <script src="/deck.js/extensions/scale/deck.scale.js" type="text/javascript"></script>
+      <script>$(function(){$.deck('.slide');});</script>
   </body>
 </html>

From 5f455a89aa57aa0dec6bf182c8a2b47557de21a0 Mon Sep 17 00:00:00 2001
From: Dave Liepmann <dave.liepmann@gmail.com>
Date: Fri, 4 Aug 2017 17:23:51 +0200
Subject: [PATCH 5/8] Add CoC Violations slide to Social Comfort section

---
 coaches_training.deck.html | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/coaches_training.deck.html b/coaches_training.deck.html
index 37d84f6..30bee5f 100644
--- a/coaches_training.deck.html
+++ b/coaches_training.deck.html
@@ -307,6 +307,17 @@ <h4>Represent the diverse and welcoming community we stand for</h4>
       </ul>
 
     </section>
+
+    <section class="slide" id="social_comfort_coc_violations">
+      <h2>Code of Conduct Violations</h2>
+
+      <p><a href="berlincodeofconduct.org">berlincodeofconduct.org</a> 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>
+
+      <h3>Q: How do I react if an attendee complains about CoC violation?</h3>
+      <h3>A: Bring them to an orga-team memeber</h3>
+
+    </section>
+
     <section class="slide" id="discussion_technical_capability">
       <h2>Discussion: Technical Capability</h2>
 

From b5555d5291131b4bcb70988d94357bbaa30debbe Mon Sep 17 00:00:00 2001
From: Dave Liepmann <dave.liepmann@gmail.com>
Date: Fri, 4 Aug 2017 17:32:23 +0200
Subject: [PATCH 6/8] Revert "Add CoC Violations slide to Social Comfort
 section"

This reverts commit 5f455a89aa57aa0dec6bf182c8a2b47557de21a0.
---
 coaches_training.deck.html | 32 +-------------------------------
 1 file changed, 1 insertion(+), 31 deletions(-)

diff --git a/coaches_training.deck.html b/coaches_training.deck.html
index 30bee5f..1267846 100644
--- a/coaches_training.deck.html
+++ b/coaches_training.deck.html
@@ -44,26 +44,7 @@ <h3>Discussion is key!</h3>
 
       <h3>Don't let the presenter(s) do all the talking!</h3>
 
-    </section>
-
-
-    <section class="slide" id="code_of_conduct">
-      <h2>Code of Conduct</h2>
-
-      <p><a href="berlincodeofconduct.org">berlincodeofconduct.org</a> 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>
-
-      <h3>Expected Behavior</h3>
-
-      <ul><li>Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.</li>
-        <li>Exercise consideration and respect in your speech and actions.</li>
-        <li>Attempt collaboration before conflict.</li>
-        <li>Refrain from demeaning, discriminatory, or harassing behavior and speech.</li>
-        <li>Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.</li>
-      </ul>
-
-    </section>
-
-
+</section>
     <section class="slide" id="why_clojurebridge">
       <h2>Why ClojureBridge?</h2>
 
@@ -307,17 +288,6 @@ <h4>Represent the diverse and welcoming community we stand for</h4>
       </ul>
 
     </section>
-
-    <section class="slide" id="social_comfort_coc_violations">
-      <h2>Code of Conduct Violations</h2>
-
-      <p><a href="berlincodeofconduct.org">berlincodeofconduct.org</a> 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>
-
-      <h3>Q: How do I react if an attendee complains about CoC violation?</h3>
-      <h3>A: Bring them to an orga-team memeber</h3>
-
-    </section>
-
     <section class="slide" id="discussion_technical_capability">
       <h2>Discussion: Technical Capability</h2>
 

From ed494ab0160fe9e796233ea2c5286a7068e54f61 Mon Sep 17 00:00:00 2001
From: Dave Liepmann <dave.liepmann@gmail.com>
Date: Fri, 4 Aug 2017 17:38:49 +0200
Subject: [PATCH 7/8] Revert "Enforce indentation"

This reverts commit 8856224e2f9991a45840962e28d1cf2fdd71d7a9.
---
 coaches_training.deck.html | 710 ++++++++++++++++++-------------------
 1 file changed, 355 insertions(+), 355 deletions(-)

diff --git a/coaches_training.deck.html b/coaches_training.deck.html
index 1267846..50aa389 100644
--- a/coaches_training.deck.html
+++ b/coaches_training.deck.html
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-          "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
   <head><meta content="text/html;charset=UTF-8" http-equiv="content-type" />
     <title>deck.rb presentation</title>
@@ -21,509 +21,509 @@
   </head>
   <body class="deck-container">
     <section class="slide" id="clojurebridge_coaches_training">
-      <h1>ClojureBridge Coaches Training</h1>
-    </section>
+<h1>ClojureBridge Coaches Training</h1>
+</section>
     <section class="slide" id="todays_agenda">
-      <h2>Today's Agenda</h2>
+<h2>Today's Agenda</h2>
 
-      <h3>Background and Practicalities</h3>
+<h3>Background and Practicalities</h3>
 
-      <h3>Discussion Topics &amp; Coaching Tips</h3>
+<h3>Discussion Topics &amp; Coaching Tips</h3>
 
-    </section>
+</section>
     <section class="slide" id="what_is_this">
-      <h2>What is this?</h2>
+<h2>What is this?</h2>
 
-      <p>You're probably at a coaches training for ClojureBridge.</p>
+<p>You're probably at a coaches training for ClojureBridge.</p>
 
-      <p>This slide deck is a tool to facilitate conversations about coaching best practices and challenges, specifically for ClojureBridge workshops.</p>
+<p>This slide deck is a tool to facilitate conversations about coaching best practices and challenges, specifically for ClojureBridge workshops.</p>
 
-      <p>It helps to have a whiteboard or those giant sticky notes for the discussions if possible.</p>
+<p>It helps to have a whiteboard or those giant sticky notes for the discussions if possible.</p>
 
-      <h3>Discussion is key!</h3>
+<h3>Discussion is key!</h3>
 
-      <h3>Don't let the presenter(s) do all the talking!</h3>
+<h3>Don't let the presenter(s) do all the talking!</h3>
 
 </section>
     <section class="slide" id="why_clojurebridge">
-      <h2>Why ClojureBridge?</h2>
+<h2>Why ClojureBridge?</h2>
 
-      <p>We're making tech more diverse and more welcoming!</p>
+<p>We're making tech more diverse and more welcoming!</p>
 
-      <h3>How?</h3>
+<h3>How?</h3>
 
-      <ul>
-        <li>We throw super-welcoming, fun, free workshops.</li>
-        <li>We provide great networking opportunities for students and volunteers.</li>
-        <li>We help our volunteers become more empathatic and better communicators.</li>
-      </ul>
+<ul>
+<li>We throw super-welcoming, fun, free workshops.</li>
+<li>We provide great networking opportunities for students and volunteers.</li>
+<li>We help our volunteers become more empathatic and better communicators.</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="introductions">
-      <h2>Introductions</h2>
+<h2>Introductions</h2>
 
-      <h3>Who are you?</h3>
+<h3>Who are you?</h3>
 
-      <ul>
-        <li>What's your name?</li>
-        <li>What are your pronouns?</li>
-        <li>Have you been to a ClojureBridge or similar workshops before? How many?</li>
-        <li>What's your favorite place in Berlin?</li>
-        <li>What's the most non-coding thing you do?</li>
-      </ul>
+<ul>
+<li>What's your name?</li>
+<li>What are your pronouns?</li>
+<li>Have you been to a ClojureBridge or similar workshops before? How many?</li>
+<li>What's your favorite place in Berlin?</li>
+<li>What's the most non-coding thing you do?</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="whats_a_clojurebridge">
-      <h2>What's a ClojureBridge?</h2>
+<h2>What's a ClojureBridge?</h2>
 
-      <p>Raise your hand if you've been to a workshop before!</p>
+<p>Raise your hand if you've been to a workshop before!</p>
 
-      <h3>RailsBridge Fun Facts</h3>
+<h3>RailsBridge Fun Facts</h3>
 
-      <ul>
-        <li>Founded in 2009</li>
-        <li>Its goal: make the community more diverse and more welcoming to newcomers.</li>
-        <li>Since 2012 backed by Bridge Foundry,</li>
-        <li>Also does MobileBridge, ng-bridge, Teaching Kids, and ... ClojureBridge!</li>
-      </ul>
+<ul>
+<li>Founded in 2009</li>
+<li>Its goal: make the community more diverse and more welcoming to newcomers.</li>
+<li>Since 2012 backed by Bridge Foundry,</li>
+<li>Also does MobileBridge, ng-bridge, Teaching Kids, and ... ClojureBridge!</li>
+</ul>
 
-      <h3>ClojureBridge</h3>
+<h3>ClojureBridge</h3>
 
-      <ul>
-        <li>First workshop April 2014</li>
-        <li>Since then over 40 workshops in the US, UK, Ireland, Australia, Scotland, Finland, Sweden, Brazil, Canada, and... Germany!</li>
-        <li>In Berlin we’ve had lots: July 2015, January 2016, June 2016, November 2016 (what a year!), and now planning for November 2017. 🎉</li>
-      </ul>
+<ul>
+<li>First workshop April 2014</li>
+<li>Since then over 40 workshops in the US, UK, Ireland, Australia, Scotland, Finland, Sweden, Brazil, Canada, and... Germany!</li>
+<li>In Berlin we’ve had lots: July 2015, January 2016, June 2016, November 2016 (what a year!), and now planning for November 2017. 🎉</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="how_does_a_workshop_work">
-      <h2>How does a workshop work?</h2>
+<h2>How does a workshop work?</h2>
 
-      <p>On Friday, we get all the necessary technologies onto the students' computers (the Installfest).</p>
+<p>On Friday, we get all the necessary technologies onto the students' computers (the Installfest).</p>
 
-      <p>The next day we start with a general introduction, then break into small groups and work through the curriculum, with some talks and breaks in between.</p>
+<p>The next day we start with a general introduction, then break into small groups and work through the curriculum, with some talks and breaks in between.</p>
 
-      <p>In groups of 3 to 4 students and two coaches we work through the curriculum (a tutorial of Clojure) and then work on a Quil app (graphics library).
-        Floating coaches are available for extra support.</p>
+<p>In groups of 3 to 4 students and two coaches we work through the curriculum (a tutorial of Clojure) and then work on a Quil app (graphics library).
+Floating coaches are available for extra support.</p>
 
-      <p>You get as far as you get, don't rush to "finish" things.</p>
+<p>You get as far as you get, don't rush to "finish" things.</p>
 
-    </section>
+</section>
     <section class="slide" id="installfest">
-      <h2>Installfest!</h2>
+<h2>Installfest!</h2>
 
-      <p>We use NightCode as editor. Of course if people have their own preference then that's fine.</p>
+<p>We use NightCode as editor. Of course if people have their own preference then that's fine.</p>
 
-      <p>NightCode is pretty easy to install, it's just an executable JAR. We'll have a couple thumb drives to go around.</p>
+<p>NightCode is pretty easy to install, it's just an executable JAR. We'll have a couple thumb drives to go around.</p>
 
-      <p>Actually create and run a Quil project, so all dependencies are downloaded and available.</p>
+<p>Actually create and run a Quil project, so all dependencies are downloaded and available.</p>
 
-      <h4>Keep in mind:</h4>
+<h4>Keep in mind:</h4>
 
-      <ul>
-        <li>There will be people with <em>all</em> kinds of computers.</li>
-        <li>Even though Windows might not be your preferred development environment, we're here to encourage people and meet them wherever they are right now.</li>
-        <li>Do NOT say bad things about Windows, even if it's frustrating.</li>
-        <li>If you're not sure about something, grab another volunteer.</li>
-      </ul>
+<ul>
+<li>There will be people with <em>all</em> kinds of computers.</li>
+<li>Even though Windows might not be your preferred development environment, we're here to encourage people and meet them wherever they are right now.</li>
+<li>Do NOT say bad things about Windows, even if it's frustrating.</li>
+<li>If you're not sure about something, grab another volunteer.</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="typical_clojurebridge_schedule">
-      <h2>Typical ClojureBridge Schedule</h2>
-
-      <ul>
-        <li><p>Friday, 6-10pm-ish: <strong>Installfest</strong> <br>get set up, meet the fellow attendees, with some nice food and drinks</p></li>
-        <li>
-          <p>Saturday's schedule</p>
-
-          <ul>
-            <li>9-9:30am: Check-in, coffee, small breakfast</li>
-            <li>9:30-10am: Opening presentation</li>
-            <li>10am-12:30pm: Class!</li>
-            <li>12:30-1:30pm: Lunch &amp; lightning talks</li>
-            <li>1:30pm-4:30pm: Class! (with a break sometime mid-afternoon)</li>
-            <li>4:30-5:00pm: Closing presentation &amp; retros</li>
-            <li>5:00pm-...: Free to hang around and socialize</li>
-          </ul>
-        </li>
-      </ul>
-
-    </section>
+<h2>Typical ClojureBridge Schedule</h2>
+
+<ul>
+<li><p>Friday, 6-10pm-ish: <strong>Installfest</strong> <br>get set up, meet the fellow attendees, with some nice food and drinks</p></li>
+<li>
+<p>Saturday's schedule</p>
+
+<ul>
+<li>9-9:30am: Check-in, coffee, small breakfast</li>
+<li>9:30-10am: Opening presentation</li>
+<li>10am-12:30pm: Class!</li>
+<li>12:30-1:30pm: Lunch &amp; lightning talks</li>
+<li>1:30pm-4:30pm: Class! (with a break sometime mid-afternoon)</li>
+<li>4:30-5:00pm: Closing presentation &amp; retros</li>
+<li>5:00pm-...: Free to hang around and socialize</li>
+</ul>
+</li>
+</ul>
+
+</section>
     <section class="slide" id="is_clojurebridge_open_source">
-      <h2>Is ClojureBridge Open Source?</h2>
+<h2>Is ClojureBridge Open Source?</h2>
 
-      <h3>WHY YES, THANK YOU FOR ASKING!</h3>
+<h3>WHY YES, THANK YOU FOR ASKING!</h3>
 
-      <h3>CLOJUREBRIDGE IS VERY OPEN SOURCE!</h3>
+<h3>CLOJUREBRIDGE IS VERY OPEN SOURCE!</h3>
 
-      <p>All the materials you're using were created by volunteers, and are on GitHub for forking and editing and using!</p>
+<p>All the materials you're using were created by volunteers, and are on GitHub for forking and editing and using!</p>
 
-      <p>If you see something that could be better, make a pull request. Pull requests are the lifeblood of ClojureBridge.</p>
+<p>If you see something that could be better, make a pull request. Pull requests are the lifeblood of ClojureBridge.</p>
 
-      <p>If you don't know how to make one, we'll help!</p>
+<p>If you don't know how to make one, we'll help!</p>
 
-    </section>
+</section>
     <section class="slide" id="is_clojurebridge_open_source">
-      <h2>Is ClojureBridge Open Source?</h2>
+<h2>Is ClojureBridge Open Source?</h2>
 
-      <h3>Curriculum</h3>
+<h3>Curriculum</h3>
 
-      <ul>
-        <li><a href="https://github.com/clojurebridge/curriculum">Github: clojurebridge/curriculum</a></li>
-        <li><a href="https://github.com/clojurebridge-berlin/curriculum">Gituhb: clojurebridge-berlin/curriculum</a></li>
-        <li><a href="https://groups.google.com/forum/#!forum/clojurebridge-curriculum">Google Groups — clojurebridge-curriculum</a></li>
-      </ul>
+<ul>
+<li><a href="https://github.com/clojurebridge/curriculum">Github: clojurebridge/curriculum</a></li>
+<li><a href="https://github.com/clojurebridge-berlin/curriculum">Gituhb: clojurebridge-berlin/curriculum</a></li>
+<li><a href="https://groups.google.com/forum/#!forum/clojurebridge-curriculum">Google Groups — clojurebridge-curriculum</a></li>
+</ul>
 
-      <h3>Our Site</h3>
+<h3>Our Site</h3>
 
-      <ul>
-        <li><a href="https://github.com/clojurebridge-berlin/clojurebridge-berlin.github.io">Github: clojurebridge-berlin/clojurebridge-berlin.github.io</a></li>
-      </ul>
+<ul>
+<li><a href="https://github.com/clojurebridge-berlin/clojurebridge-berlin.github.io">Github: clojurebridge-berlin/clojurebridge-berlin.github.io</a></li>
+</ul>
 
-      <h3>Our Wiki</h3>
+<h3>Our Wiki</h3>
 
-      <ul>
-        <li><a href="https://github.com/clojurebridge-berlin/organization/wiki">https://github.com/clojurebridge-berlin/organization/wiki</a></li>
-      </ul>
+<ul>
+<li><a href="https://github.com/clojurebridge-berlin/organization/wiki">https://github.com/clojurebridge-berlin/organization/wiki</a></li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="discussion_topics">
-      <h1>Discussion Topics</h1>
-    </section>
+<h1>Discussion Topics</h1>
+</section>
     <section class="slide" id="how_to_make_your_class_awesome">
-      <h2>How to make your class awesome</h2>
+<h2>How to make your class awesome</h2>
 
-      <p>How to make your class awesome? We created some arbitrary categories for discussion. We'll go through each one, and get input from the group (whiteboard \o/), and then provide some additional ideas and suggestions.</p>
+<p>How to make your class awesome? We created some arbitrary categories for discussion. We'll go through each one, and get input from the group (whiteboard \o/), and then provide some additional ideas and suggestions.</p>
 
-      <h3>Social Comfort</h3>
+<h3>Social Comfort</h3>
 
-      <h3>Technical Capability</h3>
+<h3>Technical Capability</h3>
 
-      <h3>Do you know what's up?</h3>
+<h3>Do you know what's up?</h3>
 
-      <h3>Challenges</h3>
+<h3>Challenges</h3>
 
-      <h3>Coaching</h3>
+<h3>Coaching</h3>
 
-      <h3>Comprehension</h3>
+<h3>Comprehension</h3>
 
-    </section>
+</section>
     <section class="slide" id="discussion_social_comfort">
-      <h2>Discussion: Social Comfort</h2>
+<h2>Discussion: Social Comfort</h2>
 
-      <h4>Imagine:</h4>
+<h4>Imagine:</h4>
 
-      <ul>
-        <li>You're trying to do something difficult</li>
-        <li>You're in a group of strangers, many of whom know how to do it better than you</li>
-        <li>You've tried before but got lost or bored or confused</li>
-        <li>You don't feel like you can articulate your thoughts and questions</li>
-        <li>You don't know the right names for anything</li>
-      </ul>
+<ul>
+<li>You're trying to do something difficult</li>
+<li>You're in a group of strangers, many of whom know how to do it better than you</li>
+<li>You've tried before but got lost or bored or confused</li>
+<li>You don't feel like you can articulate your thoughts and questions</li>
+<li>You don't know the right names for anything</li>
+</ul>
 
-      <h4>When was the last time you felt this way?</h4>
+<h4>When was the last time you felt this way?</h4>
 
-      <h4>How can we help make this easier?</h4>
+<h4>How can we help make this easier?</h4>
 
-      <h4>How can you help people feel socially comfortable?</h4>
+<h4>How can you help people feel socially comfortable?</h4>
 
-      <p>DISCUSS!</p>
+<p>DISCUSS!</p>
 
-    </section>
+</section>
     <section class="slide" id="social_comfort_ideas">
-      <h2>Social Comfort (Ideas)</h2>
+<h2>Social Comfort (Ideas)</h2>
 
-      <h4>Introductions</h4>
+<h4>Introductions</h4>
 
-      <ul>
-        <li>Include name, profession, why are you here / goals for today's class, and something silly.</li>
-        <li>Don't rush, even if you have a big class.</li>
-        <li>If someone joins the class late, ask them to introduce themselves.</li>
-      </ul>
+<ul>
+<li>Include name, profession, why are you here / goals for today's class, and something silly.</li>
+<li>Don't rush, even if you have a big class.</li>
+<li>If someone joins the class late, ask them to introduce themselves.</li>
+</ul>
 
-      <h4>Icebreakers</h4>
+<h4>Icebreakers</h4>
 
-      <ul>
-        <li>Name games! Admit up front that most people are bad at learning new names.</li>
-        <li>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.</li>
-      </ul>
+<ul>
+<li>Name games! Admit up front that most people are bad at learning new names.</li>
+<li>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.</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="social_comfort_more_ideas">
-      <h2>Social Comfort (More Ideas)</h2>
+<h2>Social Comfort (More Ideas)</h2>
 
-      <h4>Try to suppress your (understandable) culturally-influenced sexism</h4>
+<h4>Try to suppress your (understandable) culturally-influenced sexism</h4>
 
-      <ul>
-        <li>Don't hit on people. No sexual advances. None. Even at the after-party.</li>
-        <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>
-        <li>Don't make gender-based generalizations ("Women are better at X, because ...")</li>
-        <li>Don't make references to people's bodies or state your opinion of them.</li>
-        <li>Don't use slurs.</li>
-      </ul>
+<ul>
+<li>Don't hit on people. No sexual advances. None. Even at the after-party.</li>
+<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>
+<li>Don't make gender-based generalizations ("Women are better at X, because ...")</li>
+<li>Don't make references to people's bodies or state your opinion of them.</li>
+<li>Don't use slurs.</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="social_comfort_pay_attention_to_pronouns">
-      <h2>Social Comfort (pay attention to pronouns)</h2>
+<h2>Social Comfort (pay attention to pronouns)</h2>
 
-      <ul>
-        <li>attendees are women and non-binary people</li>
-        <li>attendees are asked to write down their pronouns on their name tags</li>
-        <li>please don't assume anybody's gender</li>
-        <li>refrain from gender specific terms like "hey guys", "hello ladies"</li>
-      </ul>
+<ul>
+<li>attendees are women and non-binary people</li>
+<li>attendees are asked to write down their pronouns on their name tags</li>
+<li>please don't assume anybody's gender</li>
+<li>refrain from gender specific terms like "hey guys", "hello ladies"</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="social_comfort_even_more_ideas">
-      <h2>Social Comfort (Even More Ideas)</h2>
+<h2>Social Comfort (Even More Ideas)</h2>
 
-      <h4>Represent the diverse and welcoming community we stand for</h4>
+<h4>Represent the diverse and welcoming community we stand for</h4>
 
-      <ul>
-        <li>Don't mock other languages or technologies.</li>
-        <li>Leave your nerdy flame wars at the door.</li>
-        <li>Windows is fine. PHP is fine. Javascript is fine.</li>
-        <li>Be genuinely interested in people's experiences. ("You built something? That's cool. What does it do?")</li>
-        <li>Appreciate that different technologies have different trade-offs. Being easily accessible is one of them.</li>
-      </ul>
+<ul>
+<li>Don't mock other languages or technologies.</li>
+<li>Leave your nerdy flame wars at the door.</li>
+<li>Windows is fine. PHP is fine. Javascript is fine.</li>
+<li>Be genuinely interested in people's experiences. ("You built something? That's cool. What does it do?")</li>
+<li>Appreciate that different technologies have different trade-offs. Being easily accessible is one of them.</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="discussion_technical_capability">
-      <h2>Discussion: Technical Capability</h2>
+<h2>Discussion: Technical Capability</h2>
 
-      <h3>How can you help people feel technically capable?</h3>
+<h3>How can you help people feel technically capable?</h3>
 
-      <h3>What kinds of insecurities might your student have?</h3>
+<h3>What kinds of insecurities might your student have?</h3>
 
-      <h3>How can you bolster their confidence?</h3>
+<h3>How can you bolster their confidence?</h3>
 
-      <p>DISCUSS!</p>
+<p>DISCUSS!</p>
 
-    </section>
+</section>
     <section class="slide" id="technical_capability_ideas">
-      <h2>Technical Capability (Ideas)</h2>
+<h2>Technical Capability (Ideas)</h2>
 
-      <h4>Being confused is normal</h4>
+<h4>Being confused is normal</h4>
 
-      <ul>
-        <li>Not knowing stuff is normal, even the pros spend half their day googling</li>
-        <li>If you keep at it it gets better, more quickly than you think</li>
-        <li>No need to make things perfect. Just build stuff, have fun!</li>
-        <li>Mistakes == Learning!</li>
-      </ul>
+<ul>
+<li>Not knowing stuff is normal, even the pros spend half their day googling</li>
+<li>If you keep at it it gets better, more quickly than you think</li>
+<li>No need to make things perfect. Just build stuff, have fun!</li>
+<li>Mistakes == Learning!</li>
+</ul>
 
-      <h4>Define technical concepts</h4>
+<h4>Define technical concepts</h4>
 
-      <ul>
-        <li>Define technical terms! Several times!</li>
-        <li>Assume anyone you're coaching has zero knowledge but infinite intelligence.</li>
-        <li>Remember people's backgrounds (Javascript, Ruby, Java, HTML/CSS,) and relate where possible.</li>
-        <li>Don't be afraid to use metaphors. If they are a cook, try a cooking analogy.</li>
-      </ul>
+<ul>
+<li>Define technical terms! Several times!</li>
+<li>Assume anyone you're coaching has zero knowledge but infinite intelligence.</li>
+<li>Remember people's backgrounds (Javascript, Ruby, Java, HTML/CSS,) and relate where possible.</li>
+<li>Don't be afraid to use metaphors. If they are a cook, try a cooking analogy.</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="technical_capability_more_ideas">
-      <h2>Technical Capability (More Ideas)</h2>
+<h2>Technical Capability (More Ideas)</h2>
 
-      <h4>Encourage collaboration and interaction</h4>
+<h4>Encourage collaboration and interaction</h4>
 
-      <ul>
-        <li>Explicitly encourage students to try to answer each other's questions.</li>
-        <li>If a question is asked, ask if anyone in the class thinks they can explain.</li>
-        <li>Be especially encouraging of the first few questions, to try to get things rolling.</li>
-        <li>Good responses to questions: "I'm glad you asked!" or "I actually wondered that, too." or "Great question!"</li>
-      </ul>
+<ul>
+<li>Explicitly encourage students to try to answer each other's questions.</li>
+<li>If a question is asked, ask if anyone in the class thinks they can explain.</li>
+<li>Be especially encouraging of the first few questions, to try to get things rolling.</li>
+<li>Good responses to questions: "I'm glad you asked!" or "I actually wondered that, too." or "Great question!"</li>
+</ul>
 
-      <h4>Be Super Positive, Always</h4>
+<h4>Be Super Positive, Always</h4>
 
-      <ul>
-        <li>Students have diverse backgrounds. Appreciate this fact.</li>
-        <li>If they aren't getting a concept, avoid anything that might shame them.</li>
-        <li>Don't be surprised when someone hasn't heard of something before.</li>
-        <li>Don't grab anyone's keyboard. Avoid taking over unless you think it's <em>really</em> necessary. Ask before you do. "Mind if I drive for a sec?" But really, don't.</li>
-      </ul>
+<ul>
+<li>Students have diverse backgrounds. Appreciate this fact.</li>
+<li>If they aren't getting a concept, avoid anything that might shame them.</li>
+<li>Don't be surprised when someone hasn't heard of something before.</li>
+<li>Don't grab anyone's keyboard. Avoid taking over unless you think it's <em>really</em> necessary. Ask before you do. "Mind if I drive for a sec?" But really, don't.</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="technical_capability_even_more_ideas">
-      <h2>Technical Capability (Even More Ideas)</h2>
+<h2>Technical Capability (Even More Ideas)</h2>
 
-      <h4>Find the right level</h4>
+<h4>Find the right level</h4>
 
-      <ul>
-        <li>Don't go too deep for your class level, but also, don't gloss over things.</li>
-        <li>When trying to be accurate, it's easy to go down a rabbit hole of specificity. Avoid.</li>
-        <li>Work with the co-coaches to make sure no one goes down that rabbit hole. Accountability!</li>
-        <li>Explain the big picture of a command <em>before</em> they type it in.
+<ul>
+<li>Don't go too deep for your class level, but also, don't gloss over things.</li>
+<li>When trying to be accurate, it's easy to go down a rabbit hole of specificity. Avoid.</li>
+<li>Work with the co-coaches to make sure no one goes down that rabbit hole. Accountability!</li>
+<li>Explain the big picture of a command <em>before</em> they type it in.
 
-          <ul>
-            <li>i.e., before typing the command to deploy to Heroku, explain the difference between localhost and Heroku.</li>
-          </ul>
-        </li>
-      </ul>
+<ul>
+<li>i.e., before typing the command to deploy to Heroku, explain the difference between localhost and Heroku.</li>
+</ul>
+</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="discussion_do_you_know_whats_up">
-      <h2>Discussion (Do you know what's up?)</h2>
+<h2>Discussion (Do you know what's up?)</h2>
 
-      <h4>How can you help people feel like you know what's going on?</h4>
+<h4>How can you help people feel like you know what's going on?</h4>
 
-      <h4>What are things you can do to help the students trust you?</h4>
+<h4>What are things you can do to help the students trust you?</h4>
 
-      <h4>What are some things to avoid?</h4>
+<h4>What are some things to avoid?</h4>
 
-      <p>DISCUSS!</p>
+<p>DISCUSS!</p>
 
-    </section>
+</section>
     <section class="slide" id="know_whats_up_ideas">
-      <h2>Know What's Up (Ideas)</h2>
+<h2>Know What's Up (Ideas)</h2>
 
-      <h4>Know what's going on</h4>
+<h4>Know what's going on</h4>
 
-      <ul>
-        <li>Mention planned breaks, lunch time</li>
-        <li>Remind students that there is a closing presentation at the end</li>
-        <li>Make sure they know where the bathroom is</li>
-        <li>Let them know they can hang around and socialize afterwards</li>
-      </ul>
+<ul>
+<li>Mention planned breaks, lunch time</li>
+<li>Remind students that there is a closing presentation at the end</li>
+<li>Make sure they know where the bathroom is</li>
+<li>Let them know they can hang around and socialize afterwards</li>
+</ul>
 
-      <h4>Establish a few ground rules</h4>
+<h4>Establish a few ground rules</h4>
 
-      <ul>
-        <li>Questions are always welcome, even if the student thinks it might be dumb. "That's a <strong>GREAT</strong> question"</li>
-        <li>Explain that if someone has trouble, the coaches will help troubleshoot.</li>
-        <li>If anyone wants to switch classes, tell them they should feel TOTALLY COMFORTABLE switching at any point.</li>
-        <li>Have breaks! Eat a muffin! Have a look at what other groups are doing!</li>
-      </ul>
+<ul>
+<li>Questions are always welcome, even if the student thinks it might be dumb. "That's a <strong>GREAT</strong> question"</li>
+<li>Explain that if someone has trouble, the coaches will help troubleshoot.</li>
+<li>If anyone wants to switch classes, tell them they should feel TOTALLY COMFORTABLE switching at any point.</li>
+<li>Have breaks! Eat a muffin! Have a look at what other groups are doing!</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="know_whats_up_more_ideas">
-      <h2>Know What's Up (More Ideas)</h2>
+<h2>Know What's Up (More Ideas)</h2>
 
-      <h4>Teaching style</h4>
+<h4>Teaching style</h4>
 
-      <ul>
-        <li>Know people's name, and use it</li>
-        <li>You can correct people in a nice and encouraging way
+<ul>
+<li>Know people's name, and use it</li>
+<li>You can correct people in a nice and encouraging way
 
-          <ul>
-            <li>"Well, this might work better and this is why."</li>
-            <li>"Can you explain how you came to that conclusion?"</li>
-            <li>"Does anyone have a different answer?"</li>
-            <li>"Ah, I see what you're trying to do."</li>
-          </ul>
-        </li>
-        <li>Ask yourself questions and answer them.</li>
-      </ul>
+<ul>
+<li>"Well, this might work better and this is why."</li>
+<li>"Can you explain how you came to that conclusion?"</li>
+<li>"Does anyone have a different answer?"</li>
+<li>"Ah, I see what you're trying to do."</li>
+</ul>
+</li>
+<li>Ask yourself questions and answer them.</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="know_whats_up_even_more_ideas">
-      <h2>Know What's Up (Even More Ideas)</h2>
+<h2>Know What's Up (Even More Ideas)</h2>
 
-      <h4>Pace yourself!</h4>
+<h4>Pace yourself!</h4>
 
-      <ul>
-        <li>Don't go too fast. You will probably go too fast. Check in occasionally to ensure everyone is still with you.</li>
-        <li>You can say the same thing THREE TIMES and it will not be boring yet.</li>
-        <li>When you ask a question, wait TEN WHOLE SECONDS before saying anything else. People need time to think.</li>
-        <li>Don't let the most advanced students dictate the pacing or answer all the questions.</li>
-      </ul>
+<ul>
+<li>Don't go too fast. You will probably go too fast. Check in occasionally to ensure everyone is still with you.</li>
+<li>You can say the same thing THREE TIMES and it will not be boring yet.</li>
+<li>When you ask a question, wait TEN WHOLE SECONDS before saying anything else. People need time to think.</li>
+<li>Don't let the most advanced students dictate the pacing or answer all the questions.</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="discussion_challenges">
-      <h2>Discussion: Challenges</h2>
+<h2>Discussion: Challenges</h2>
 
-      <p>Talk about what problems you might anticipate, and what to do about them.</p>
+<p>Talk about what problems you might anticipate, and what to do about them.</p>
 
-      <h4>Some issues:</h4>
+<h4>Some issues:</h4>
 
-      <ul>
-        <li>Student is in the wrong class level</li>
-        <li>Student is disruptive</li>
-        <li>Student is disengaged</li>
-      </ul>
+<ul>
+<li>Student is in the wrong class level</li>
+<li>Student is disruptive</li>
+<li>Student is disengaged</li>
+</ul>
 
-      <p>DISCUSS!</p>
+<p>DISCUSS!</p>
 
-    </section>
+</section>
     <section class="slide" id="discussion_coaching">
-      <h2>Discussion: Coaching</h2>
+<h2>Discussion: Coaching</h2>
 
-      <h4>What are the benefits of having two coaches in a group?</h4>
+<h4>What are the benefits of having two coaches in a group?</h4>
 
-      <h4>How can you divide the roles between the coaches?</h4>
+<h4>How can you divide the roles between the coaches?</h4>
 
-      <h4>How can you get a good dynamic between the whole team, both attendees and coaches?</h4>
+<h4>How can you get a good dynamic between the whole team, both attendees and coaches?</h4>
 
-      <p>DISCUSS!</p>
+<p>DISCUSS!</p>
 
-    </section>
+</section>
     <section class="slide" id="coaching_build_a_team">
-      <h2>Coaching: Build a Team</h2>
+<h2>Coaching: Build a Team</h2>
 
-      <ul>
-        <li>ClojureBridge normally makes a distinction between coaches and TAs (teaching assistants).</li>
-        <li>We will try to form groups with two coaches per group.</li>
-        <li>You can decide on one coach to take the lead, or you can tag-team.</li>
-        <li>There will also be some "floating" TAs that can go around and help.</li>
-      </ul>
+<ul>
+<li>ClojureBridge normally makes a distinction between coaches and TAs (teaching assistants).</li>
+<li>We will try to form groups with two coaches per group.</li>
+<li>You can decide on one coach to take the lead, or you can tag-team.</li>
+<li>There will also be some "floating" TAs that can go around and help.</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="coaching_dynamics_ideas">
-      <h2>Coaching Dynamics (Ideas)</h2>
+<h2>Coaching Dynamics (Ideas)</h2>
 
-      <ul>
-        <li>Talk with your co-coach beforehand to set expectations</li>
-        <li>It can make sense to have one person take the lead</li>
-        <li>The other coach can give more individual assistance</li>
-        <li>Swap these roles around if it makes sense. Find a healthy dynamic!</li>
-      </ul>
+<ul>
+<li>Talk with your co-coach beforehand to set expectations</li>
+<li>It can make sense to have one person take the lead</li>
+<li>The other coach can give more individual assistance</li>
+<li>Swap these roles around if it makes sense. Find a healthy dynamic!</li>
+</ul>
 
-      <h4>Co-coaching (Some Ideas)</h4>
+<h4>Co-coaching (Some Ideas)</h4>
 
-      <ul>
-        <li>Both coaches can ask questions to encourage students to speak up.</li>
-        <li>Ask your co-coach to explain a concept; they may be more technically advanced than you!</li>
-        <li>Co-coaches can help people who get lost.</li>
-        <li>If someone falls behind, the co-coach can take them aside to do some 1-on-1.</li>
-      </ul>
+<ul>
+<li>Both coaches can ask questions to encourage students to speak up.</li>
+<li>Ask your co-coach to explain a concept; they may be more technically advanced than you!</li>
+<li>Co-coaches can help people who get lost.</li>
+<li>If someone falls behind, the co-coach can take them aside to do some 1-on-1.</li>
+</ul>
 
-    </section>
+</section>
     <section class="slide" id="discussion_comprehension">
-      <h2>Discussion: Comprehension</h2>
+<h2>Discussion: Comprehension</h2>
 
-      <h4>How can you tell if they understand the words you're saying?</h4>
+<h4>How can you tell if they understand the words you're saying?</h4>
 
-      <h4>What are good questions to ask to check comprehension?</h4>
+<h4>What are good questions to ask to check comprehension?</h4>
 
-      <h4>What did your favorite coaches do to gauge understanding?</h4>
+<h4>What did your favorite coaches do to gauge understanding?</h4>
 
-      <p>DISCUSS!</p>
+<p>DISCUSS!</p>
 
-    </section>
+</section>
     <section class="slide" id="practical_recap">
-      <h2>Practical Recap</h2>
+<h2>Practical Recap</h2>
 
-      <p>Installfest: Friday <strong>25 November, 18:00</strong></p>
+<p>Installfest: Friday <strong>25 November, 18:00</strong></p>
 
-      <p>Workshop: Saturday <strong>26 November</strong>, doors open at <strong>9:00</strong>, starts at 9:30</p>
+<p>Workshop: Saturday <strong>26 November</strong>, doors open at <strong>9:00</strong>, starts at 9:30</p>
 
-      <p>Afterparty: at Volksbar</p>
+<p>Afterparty: at Volksbar</p>
 
-      <p> </p>
+<p> </p>
 
-      <p>Location: <strong>Wunderlist office (Microsoft)</strong></p>
+<p>Location: <strong>Wunderlist office (Microsoft)</strong></p>
 
-      <p>Karl-Liebknecht-Straße 32</p>
+<p>Karl-Liebknecht-Straße 32</p>
 
-      <p>Around the corner from <strong>Alexanderplatz</strong>.</p>
+<p>Around the corner from <strong>Alexanderplatz</strong>.</p>
 
-      <p> </p>
+<p> </p>
 
-      <p>Don't forget: laptop, powercord</p>
+<p>Don't forget: laptop, powercord</p>
 
-      <p>Go through the curriculum at home.</p>
+<p>Go through the curriculum at home.</p>
 
-    </section>
+</section>
     <a class="deck-prev-link" href="#" title="Previous"></a><a class="deck-next-link" href="#" title="Next"></a>    <div class="slide_toc">      <div class="toggle">[contents]</div>
       <div class="table">
         <h2>deck.rb presentation</h2>
@@ -567,30 +567,30 @@ <h2>deck.rb presentation</h2>
     <form action="." class="goto-form" method="get"><label for="goto-slide">Go to slide:</label><input id="goto-slide" list="goto-datalist" name="slidenum" type="text" />
       <datalist id="goto-datalist"></datalist>
       <input type="submit" value="Go" /></form>
-      <a class="deck-permalink" href="." title="Permalink to this slide">#</a>
-      <script src="/deck.js/modernizr.custom.js"></script>
-      <script src="/deck.js/jquery-1.7.2.min.js"></script>
-      <script type="text/javascript">
-       // <![CDATA[
-
-       jQuery(document).ready(function($){
-           $('.slide_toc .toggle').click(function(){
-               $('.slide_toc .table').toggle();
-           });
-
-       });
-       // ]]>
-      </script>
-
-      <!--Deck Core and extensions-->
-
-      <script src="/deck.js/core/deck.core.js" type="text/javascript"></script>
-      <script src="/deck.js/extensions/goto/deck.goto.js" type="text/javascript"></script>
-      <script src="/deck.js/extensions/menu/deck.menu.js" type="text/javascript"></script>
-      <script src="/deck.js/extensions/navigation/deck.navigation.js" type="text/javascript"></script>
-      <script src="/deck.js/extensions/status/deck.status.js" type="text/javascript"></script>
-      <script src="/deck.js/extensions/hash/deck.hash.js" type="text/javascript"></script>
-      <script src="/deck.js/extensions/scale/deck.scale.js" type="text/javascript"></script>
-      <script>$(function(){$.deck('.slide');});</script>
+    <a class="deck-permalink" href="." title="Permalink to this slide">#</a>
+    <script src="/deck.js/modernizr.custom.js"></script>
+    <script src="/deck.js/jquery-1.7.2.min.js"></script>
+    <script type="text/javascript">
+// <![CDATA[
+
+jQuery(document).ready(function($){
+    $('.slide_toc .toggle').click(function(){
+      $('.slide_toc .table').toggle();
+    });
+
+});
+// ]]>
+    </script>
+
+<!--Deck Core and extensions-->
+
+    <script src="/deck.js/core/deck.core.js" type="text/javascript"></script>
+    <script src="/deck.js/extensions/goto/deck.goto.js" type="text/javascript"></script>
+    <script src="/deck.js/extensions/menu/deck.menu.js" type="text/javascript"></script>
+    <script src="/deck.js/extensions/navigation/deck.navigation.js" type="text/javascript"></script>
+    <script src="/deck.js/extensions/status/deck.status.js" type="text/javascript"></script>
+    <script src="/deck.js/extensions/hash/deck.hash.js" type="text/javascript"></script>
+    <script src="/deck.js/extensions/scale/deck.scale.js" type="text/javascript"></script>
+    <script>$(function(){$.deck('.slide');});</script>
   </body>
 </html>

From 8a36ea0a5df4dd5af5c9d134daa97e2f51ea9cbb Mon Sep 17 00:00:00 2001
From: Dave Liepmann <dave.liepmann@gmail.com>
Date: Fri, 4 Aug 2017 17:42:15 +0200
Subject: [PATCH 8/8] Derp, next isn't November. Rephrase.

---
 coaches_training.deck.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/coaches_training.deck.html b/coaches_training.deck.html
index 50aa389..95ded57 100644
--- a/coaches_training.deck.html
+++ b/coaches_training.deck.html
@@ -92,7 +92,7 @@ <h3>ClojureBridge</h3>
 <ul>
 <li>First workshop April 2014</li>
 <li>Since then over 40 workshops in the US, UK, Ireland, Australia, Scotland, Finland, Sweden, Brazil, Canada, and... Germany!</li>
-<li>In Berlin we’ve had lots: July 2015, January 2016, June 2016, November 2016 (what a year!), and now planning for November 2017. 🎉</li>
+<li>In Berlin we’ve had lots: July 2015, January 2016, June 2016, November 2016 (what a year!), and now autumn 2017. 🎉</li>
 </ul>
 
 </section>