Skip to content

Discussion reorderings etc #85

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
Sep 28, 2017
Merged

Discussion reorderings etc #85

Show file tree
Hide file tree
Changes from 9 commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
0746329
Minor spacing issues
socksy Sep 27, 2017
ab55b84
Shorten the intro round
socksy Sep 27, 2017
b9036ea
Move CoC stuff to beginning before discussion points
socksy Sep 27, 2017
be67fe4
Move discussions to be all together, answers afterwards
socksy Sep 27, 2017
3693eb5
Move CoC violation stuff
socksy Sep 27, 2017
a33df41
Cursory curriculum overview
socksy Sep 27, 2017
a24d716
Use bundix to allow nix-shell to use jekyll/deck
socksy Sep 27, 2017
5992bb4
Merge branch 'nix-support' into discussion-reorderings-etc
socksy Sep 27, 2017
67d591a
Compiled coaches training changes to HTML
socksy Sep 27, 2017
c6492e6
Capitalization typo on 'curriculum'
socksy Sep 27, 2017
f6e5a2b
Add restaurant question, and quil mention in curriculum
socksy Sep 28, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
231 changes: 124 additions & 107 deletions coaches_training.deck.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ <h3>Don't let the presenter(s) do all the talking!</h3>
<section class="slide" id="code_of_conduct">
<h2>Code of Conduct</h2>

<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>
<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>

<h3>Expected Behavior</h3>

Expand Down Expand Up @@ -89,19 +89,14 @@ <h2>Introductions</h2>
<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>
<li>What's your name and pronouns?</li>
<li>Have you been to a ClojureBridge or similar workshops before?</li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I liked having one other non-programming related question. Maybe "fun fact about yourself" or "your favourite restaurant" or something. Or even "how did you hear about ClojureBridge"

Copy link
Member Author

@socksy socksy Sep 28, 2017 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reaosning behind this was that the whole time before you speak, you are worrying about what to say, and barely remember other people's answers anyway... At the same time, this part is also takes a while, so it's nice to be able to reduce it to a friendly names round.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am in favor of shortening it, but I hear Franka's point about keeping one (and only one) non-programming question. I vote "favorite place in Berlin" because it's easy and revealing without being intrusive.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given there are gonna be people not from Berlin there, I suspect another one would be better (fav. restaurant?) Though I am still personally skeptical about having it

</ul>

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

<p>Raise your hand if you've been to a workshop before!</p>

<h3>RailsBridge Fun Facts</h3>

<ul>
Expand Down Expand Up @@ -140,7 +135,7 @@ <h2>Installfest!</h2>

<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>

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

<h4>Keep in mind:</h4>

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

</section>
<section class="slide" id="on_that_note">
<h2>On that note...</h2>

<ul>
<li>Don't be negative about technologies, even if you're certain they're the work of the devil</li>
<li>PHP is fine, Windows is fine, VisualBasic is fine</li>
<li>Appreciate that different technologies have different trade-offs. Being easily accessible is one of them.</li>
</ul>

</section>
<section class="slide" id="try_to_suppress_your_understandable_culturallyinfluenced_sexism">
<h2>Try to suppress your (understandable) culturally-influenced sexism</h2>

<ul>
<li>Don't hit on people. No sexual advances. This extends to 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 class="slide" id="typical_clojurebridge_schedule">
<h2>Typical ClojureBridge Schedule</h2>
Expand Down Expand Up @@ -245,6 +262,66 @@ <h4>How can you help people feel socially comfortable?</h4>

<p>DISCUSS!</p>

</section>
<section class="slide" id="discussion_do_you_know_whats_up">
<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>What are things you can do to help the students trust you?</h4>

<h4>What are some things to avoid?</h4>

<p>DISCUSS!</p>

</section>
<section class="slide" id="discussion_technical_capability">
<h2>Discussion: Technical Capability</h2>

<h3>How can you help people feel technically capable?</h3>

<h3>What kinds of insecurities might your student have?</h3>

<h3>How can you bolster their confidence?</h3>

<p>DISCUSS!</p>

</section>
<section class="slide" id="discussion_challenges">
<h2>Discussion: Challenges</h2>

<p>Talk about what problems you might anticipate, and what to do about them.</p>

<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>

<p>DISCUSS!</p>

</section>
<section class="slide" id="discussion_coaching">
<h2>Discussion: Coaching</h2>

<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 get a good dynamic between the whole team, both attendees and coaches?</h4>

<p>DISCUSS!</p>

</section>
<section class="slide" id="what_we_came_up_with">
<h2>What we came up with</h2>

<ul>
<li>So now you've been through these discussions, this is what we came up with!</li>
</ul>

</section>
<section class="slide" id="social_comfort_ideas">
<h2>Social Comfort (Ideas)</h2>
Expand All @@ -266,18 +343,7 @@ <h4>Icebreakers</h4>

</section>
<section class="slide" id="social_comfort_more_ideas">
<h2>Social Comfort (More Ideas)</h2>

<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>

<h1>Social Comfort (More Ideas)</h1>
</section>
<section class="slide" id="social_comfort_pay_attention_to_pronouns">
<h2>Social Comfort (pay attention to pronouns)</h2>
Expand All @@ -289,42 +355,6 @@ <h2>Social Comfort (pay attention to pronouns)</h2>
<li>refrain from gender specific terms like "hey guys", "hello ladies"</li>
</ul>

</section>
<section class="slide" id="social_comfort_even_more_ideas">
<h2>Social Comfort (Even More Ideas)</h2>

<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>

</section>
<section class="slide" id="code_of_conduct_violations">
<h2>Code of Conduct Violations</h2>

<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>

<h4>Q: How do I react if an attendee complains about CoC violation?</h4>

<h4>A: Bring them to an orga-team member</h4>

</section>
<section class="slide" id="discussion_technical_capability">
<h2>Discussion: Technical Capability</h2>

<h3>How can you help people feel technically capable?</h3>

<h3>What kinds of insecurities might your student have?</h3>

<h3>How can you bolster their confidence?</h3>

<p>DISCUSS!</p>

</section>
<section class="slide" id="technical_capability_ideas">
<h2>Technical Capability (Ideas)</h2>
Expand Down Expand Up @@ -387,18 +417,6 @@ <h4>Find the right level</h4>
</li>
</ul>

</section>
<section class="slide" id="discussion_do_you_know_whats_up">
<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>What are things you can do to help the students trust you?</h4>

<h4>What are some things to avoid?</h4>

<p>DISCUSS!</p>

</section>
<section class="slide" id="know_whats_up_ideas">
<h2>Know What's Up (Ideas)</h2>
Expand Down Expand Up @@ -455,42 +473,23 @@ <h4>Pace yourself!</h4>
</ul>

</section>
<section class="slide" id="discussion_challenges">
<h2>Discussion: Challenges</h2>

<p>Talk about what problems you might anticipate, and what to do about them.</p>

<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>

<p>DISCUSS!</p>

</section>
<section class="slide" id="discussion_coaching">
<h2>Discussion: Coaching</h2>

<h4>What are the benefits of having two coaches in a group?</h4>
<section class="slide" id="code_of_conduct_violations">
<h2>Code of Conduct Violations</h2>

<h4>How can you divide the roles between the coaches?</h4>
<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>

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

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

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

<ul>
<li>ClojureBridge normally makes a distinction between coaches and TAs (teaching assistants).</li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 For removing this

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

<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>
<li>There will also be some "floating" coaches that can go around and help.</li>
</ul>

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

</section>
<section class="slide" id="discussion_comprehension">
<h2>Discussion: Comprehension</h2>
<section class="slide" id="the_curriculum">
<h2>The Curriculum</h2>

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

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

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

<p>DISCUSS!</p>
<ul>
<li>values</li>
<li>data structures</li>
<li>functions</li>
<li>control logic</li>
</ul>

<h2>Please take a look :)</h2>

</section>
<section class="slide" id="some_people_are_trialing_a_new_curriculum">
<h2>Some people are trialing a new Curriculum</h2>

<p>But everyone should still install NightCode for now</p>

</section>
<section class="slide" id="practical_recap">
Expand Down Expand Up @@ -569,30 +583,33 @@ <h2>deck.rb presentation</h2>
<li><a href="#whats_a_clojurebridge">What&#39;s a ClojureBridge?</a></li>
<li><a href="#how_does_a_workshop_work">How does a workshop work?</a></li>
<li><a href="#installfest">Installfest!</a></li>
<li><a href="#on_that_note">On that note...</a></li>
<li><a href="#try_to_suppress_your_understandable_culturallyinfluenced_sexism">Try to suppress your (understandable) culturally-influenced sexism</a></li>
<li><a href="#typical_clojurebridge_schedule">Typical ClojureBridge Schedule</a></li>
<li><a href="#is_clojurebridge_open_source">Is ClojureBridge Open Source?</a></li>
<li><a href="#is_clojurebridge_open_source">Is ClojureBridge Open Source?</a></li>
<li><a href="#discussion_topics">Discussion Topics</a></li>
<li><a href="#how_to_make_your_class_awesome">How to make your class awesome</a></li>
<li><a href="#discussion_social_comfort">Discussion: Social Comfort</a></li>
<li><a href="#discussion_do_you_know_whats_up">Discussion (Do you know what&#39;s up?)</a></li>
<li><a href="#discussion_technical_capability">Discussion: Technical Capability</a></li>
<li><a href="#discussion_challenges">Discussion: Challenges</a></li>
<li><a href="#discussion_coaching">Discussion: Coaching</a></li>
<li><a href="#what_we_came_up_with">What we came up with</a></li>
<li><a href="#social_comfort_ideas">Social Comfort (Ideas)</a></li>
<li><a href="#social_comfort_more_ideas">Social Comfort (More Ideas)</a></li>
<li><a href="#social_comfort_pay_attention_to_pronouns">Social Comfort (pay attention to pronouns)</a></li>
<li><a href="#social_comfort_even_more_ideas">Social Comfort (Even More Ideas)</a></li>
<li><a href="#code_of_conduct_violations">Code of Conduct Violations</a></li>
<li><a href="#discussion_technical_capability">Discussion: Technical Capability</a></li>
<li><a href="#technical_capability_ideas">Technical Capability (Ideas)</a></li>
<li><a href="#technical_capability_more_ideas">Technical Capability (More Ideas)</a></li>
<li><a href="#technical_capability_even_more_ideas">Technical Capability (Even More Ideas)</a></li>
<li><a href="#discussion_do_you_know_whats_up">Discussion (Do you know what&#39;s up?)</a></li>
<li><a href="#know_whats_up_ideas">Know What&#39;s Up (Ideas)</a></li>
<li><a href="#know_whats_up_more_ideas">Know What&#39;s Up (More Ideas)</a></li>
<li><a href="#know_whats_up_even_more_ideas">Know What&#39;s Up (Even More Ideas)</a></li>
<li><a href="#discussion_challenges">Discussion: Challenges</a></li>
<li><a href="#discussion_coaching">Discussion: Coaching</a></li>
<li><a href="#code_of_conduct_violations">Code of Conduct Violations</a></li>
<li><a href="#coaching_build_a_team">Coaching: Build a Team</a></li>
<li><a href="#coaching_dynamics_ideas">Coaching Dynamics (Ideas)</a></li>
<li><a href="#discussion_comprehension">Discussion: Comprehension</a></li>
<li><a href="#the_curriculum">The Curriculum</a></li>
<li><a href="#some_people_are_trialing_a_new_curriculum">Some people are trialing a new Curriculum</a></li>
<li><a href="#practical_recap">Practical Recap</a></li>
</ul>
</div>
Expand Down
11 changes: 11 additions & 0 deletions default.nix
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
with (import <nixpkgs> {});
let
gems = bundlerEnv {
name = "clojurebridge-website";
inherit ruby;
gemdir = ./.;
};
in stdenv.mkDerivation {
name = "clojurebridge-website";
buildInputs = [gems ruby];
}
Loading