Skip to content

Commit

Permalink
Merge pull request #6 from lehmannro/gh-pages
Browse files Browse the repository at this point in the history 
Enhancing the guide's utility
  • Loading branch information
@gnunicorn
gnunicorn committed Apr 17, 2013
2 parents ddb6ac8 + 2f9492e commit 9463e9a
Showing 1 changed file with 77 additions and 14 deletions.
91 changes: 77 additions & 14 deletions presentations/coaching/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -68,18 +68,39 @@ <h2>Introduction to Coaching</h2>
<header>
<h2>The Material</h2>
</header>
<p>We strongly believe the best way to learn to code -- or any other tech-related subject, for that matter -- is with a hands-on, experience-oriented, and pragmatic workshop that someone can work through at their own pace. Our curricula are designed for exactly that purpose.</p>
<p>We strongly believe the best way to learn to code &mdash; or any other tech-related subject, for that matter &mdash; is with a <strong>hands-on</strong>, <strong>experience-oriented</strong>, and <strong>pragmatic</strong> workshop that someone can work through <strong>at their own pace</strong>. Our curricula are designed for exactly that purpose.</p>
<p>This is also reflected in the way we organise ourselves on site: there is no classroom-style setting; everyone has their own workspace instead. There is no teacher in front and no one going through the material with a presenter.</p>
</section>
</div></div>

<div class="slide" id="coaching_aint_teaching"><div>
<div class="slide" id="didactic_style"><div>
<section>
<header>
<h2>Coaching isn't teaching...</h2>
<h2>A note about the material</h2>
</header>
<p>in the sense that we are not standing in front and teaching here. Coaches</p>
<p>
<ul>
<li>At times, the material might seem unnecessarily dense to you, as if going through extra hoops.</li>
<li>Don't fret, that is on purpose!</li>
<li>We believe in learning exploratively (sometimes called <em>the hard way</em>.)</li>
<li>That means teaching them a little suboptimal style first, just to make them discover <strong>themselves</strong> how (and why!) to do it better. Example:
<ul>
<li>Writing an expression you want repeated out five times at first.</li>
<li>To make them understand how powerful and convenient loops are.</li>
</ul>
</li>
</ul>
</p>
</section>
</div></div>

<div class="slide" id="coaching_aint_teaching"><div>
<section>
<header>
<h2>Coaching isn't teaching&hellip;</h2>
</header>
<p>in the sense that we are not standing in front and teaching here.</p>
<p>Coaches&hellip;
<ul>
<li>Stand by on the sidelines</li>
<li>Are right there when needed</li>
Expand All @@ -96,6 +117,7 @@ <h2>Coaching isn't teaching...</h2>
<section>
<header>
<h2>Creating a friendly environment</h2>
Atmosphere
</header>
<p>
<ul>
Expand All @@ -114,16 +136,17 @@ <h2>Creating a friendly environment</h2>
<div class="slide" id="friendly_environment_2"><div>
<section>
<header>
<h2>Creating a friendly environment, part 2</h2>
<h2>Creating a friendly environment</h2>
Encouragement
</header>
<p>
<ul>
<li>Assume everyone you're coaching has zero knowledge but infinite intelligence</li>
<li>Encourage learners to ask questions</li>
<li>Respond positively</li>
<li>Use normal language instead of slang</li>
<li>Make sure the learner understood what you said</li>
<li>and explain it again differently if that's not the case</li>
<li>Encourage learners to play around on their own</li>
<li>Whatever they do is great and beautiful!</li>
</ul>
</p>
</section>
Expand All @@ -132,15 +155,19 @@ <h2>Creating a friendly environment, part 2</h2>
<div class="slide" id="friendly_environment_3"><div>
<section>
<header>
<h2>Creating a friendly environment, part 3</h2>
<h2>Creating a friendly environment</h2>
Questions
</header>
<p>
<ul>
<li>Look around to see if someone else might be having trouble</li>
<li>They might just be afraid to ask</li>
<li>Come by once in a while and ask: "Hey, how is it going? Anything I can help you with?"</li>
<li>Before you start typing on a learners computer, ask whether that is okay with them</li>
<li>Encourage learners to play around on their own</li>
<li>Come by once in a while and ask: &ldquo;Hey, how is it going? Anything I can help you with?&rdquo;
<ul>
<li>This is a very powerful tool: It helps shy learners, builds rapport and increases engagement.</li>
<li>Another trick: Sit next to them and chat about what they are doing.</li>
</ul>
</li>
</ul>
</p>
</section>
Expand All @@ -157,21 +184,21 @@ <h2>Questions are good!</h2>
<li>Emphasize that there is no such thing as "dumb" questions</li>
<li>Ask if learners have any questions</li>
<li>Give other learners the chance to try to answer that question</li>
<li>Coding is collaboration - make sure learners understand that</li>
<li>Coding is collaboration &mdash; make sure learners understand that</li>
</ul>
</p>
</section>
</div></div>

<div class="slide" id="repsonding_to_questions"><div>
<div class="slide" id="responding_to_questions"><div>
<section>
<header>
<h2>Responding to questions</h2>
</header>
<p>
Chances are, there is a specific question when the learner asks you to help them. How do you respond?
<ul>
<li><strong>Positevly</strong>:
<li><strong>Positively</strong>:
<ul>
<li>"I’m glad you asked that."</li>
<li>"What an interesting question!"</li>
Expand All @@ -180,11 +207,29 @@ <h2>Responding to questions</h2>
</ul>
</li>
<li>If in doubt: blame the material, never the learner.</li>
<li>Their interpretation of the material might be as good as ours!</li>
</ul>
</p>
</section>
</div></div>

<div class="slide" id="responding_to_questions_1"><div>
<section>
<header>
<h2>Responding to questions, aftermath</h2>
</header>
<p>
Question solved. Now what?
<ul>
<li>We strive to continuously improve our material.</li>
<li>Try to write down the notion of the question so you don't forget it.</li>
<li>File a ticket after the workshop (Github Issues.)</li>
</ul>
</p>
</section>
</div></div>


<div class="slide" id="pacing"><div>
<section>
<header>
Expand Down Expand Up @@ -239,6 +284,24 @@ <h2>Don'ts</h2>
<li>We do not use the time to advertise our own companies/jobs/ourselves</li>
<li>We do not pick on or make fun of anyone or anything (not even PHP!)</li>
<li>We do <strong>not debate</strong> which programming language, methods or technologies are "better"</li>
<li>We do not touch their keyboard</li>
</ul>
</p>
</section>
</div></div>

<div class="slide" id="donts_keyboard"><div>
<section>
<header>
<p>Their keyboard</p>
<h2>it is made of <strong style="color: red;">lava!</strong></h2>
</header>
<p>
<ul>
<li>Learners <strong>are</strong> going to drift away when you take over their keyboard.</li>
<li>Don't touch it.</li>
<li>If you absolutely, ultimatively <em>must</em> type something on their computer &mdash; chances are you don't &mdash;, ask whether that is okay with them.</li>
<li>And explain what you are doing.</li>
</ul>
</p>
</section>
Expand Down

0 comments on commit 9463e9a

Please sign in to comment.