diff --git a/presentations/coaching/index.html b/presentations/coaching/index.html index 9fef4ea..be15e27 100644 --- a/presentations/coaching/index.html +++ b/presentations/coaching/index.html @@ -68,18 +68,39 @@

Introduction to Coaching

The Material

-

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.

+

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.

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.

-
+
-

Coaching isn't teaching...

+

A note about the material

-

in the sense that we are not standing in front and teaching here. Coaches

+

    +
  • At times, the material might seem unnecessarily dense to you, as if going through extra hoops.
  • +
  • Don't fret, that is on purpose!
  • +
  • We believe in learning exploratively (sometimes called the hard way.)
  • +
  • That means teaching them a little suboptimal style first, just to make them discover themselves how (and why!) to do it better. Example: +
      +
    • Writing an expression you want repeated out five times at first.
    • +
    • To make them understand how powerful and convenient loops are.
    • +
    +
  • +
+

+
+
+ +
+
+
+

Coaching isn't teaching…

+
+

in the sense that we are not standing in front and teaching here.

+

Coaches…

  • Stand by on the sidelines
  • Are right there when needed
  • @@ -96,6 +117,7 @@

    Coaching isn't teaching...

    Creating a friendly environment

    + Atmosphere

      @@ -114,16 +136,17 @@

      Creating a friendly environment

      -

      Creating a friendly environment, part 2

      +

      Creating a friendly environment

      + Encouragement

      • Assume everyone you're coaching has zero knowledge but infinite intelligence
      • -
      • Encourage learners to ask questions
      • -
      • Respond positively
      • Use normal language instead of slang
      • Make sure the learner understood what you said
      • and explain it again differently if that's not the case
      • +
      • Encourage learners to play around on their own
      • +
      • Whatever they do is great and beautiful!

      @@ -132,15 +155,19 @@

      Creating a friendly environment, part 2

      -

      Creating a friendly environment, part 3

      +

      Creating a friendly environment

      + Questions

      • Look around to see if someone else might be having trouble
      • They might just be afraid to ask
      • -
      • Come by once in a while and ask: "Hey, how is it going? Anything I can help you with?"
      • -
      • Before you start typing on a learners computer, ask whether that is okay with them
      • -
      • Encourage learners to play around on their own
      • +
      • Come by once in a while and ask: “Hey, how is it going? Anything I can help you with?” +
          +
        • This is a very powerful tool: It helps shy learners, builds rapport and increases engagement.
        • +
        • Another trick: Sit next to them and chat about what they are doing.
        • +
        +

      @@ -157,13 +184,13 @@

      Questions are good!

    • Emphasize that there is no such thing as "dumb" questions
    • Ask if learners have any questions
    • Give other learners the chance to try to answer that question
    • -
    • Coding is collaboration - make sure learners understand that
    • +
    • Coding is collaboration — make sure learners understand that

-
+

Responding to questions

@@ -171,7 +198,7 @@

Responding to questions

Chances are, there is a specific question when the learner asks you to help them. How do you respond?

    -
  • Positevly: +
  • Positively:
    • "I’m glad you asked that."
    • "What an interesting question!"
    • @@ -180,11 +207,29 @@

      Responding to questions

  • If in doubt: blame the material, never the learner.
  • +
  • Their interpretation of the material might be as good as ours!

+
+
+
+

Responding to questions, aftermath

+
+

+ Question solved. Now what? +

    +
  • We strive to continuously improve our material.
  • +
  • Try to write down the notion of the question so you don't forget it.
  • +
  • File a ticket after the workshop (Github Issues.)
  • +
+

+
+
+ +
@@ -239,6 +284,24 @@

Don'ts

  • We do not use the time to advertise our own companies/jobs/ourselves
  • We do not pick on or make fun of anyone or anything (not even PHP!)
  • We do not debate which programming language, methods or technologies are "better"
  • +
  • We do not touch their keyboard
  • + +

    +
    +
    + +
    +
    +
    +

    Their keyboard

    +

    it is made of lava!

    +
    +

    +

      +
    • Learners are going to drift away when you take over their keyboard.
    • +
    • Don't touch it.
    • +
    • If you absolutely, ultimatively must type something on their computer — chances are you don't —, ask whether that is okay with them.
    • +
    • And explain what you are doing.