diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..1c563ae --- /dev/null +++ b/.gitignore @@ -0,0 +1,2 @@ +.DS_Store +_site \ No newline at end of file diff --git a/presentations/coaching/index.html b/presentations/coaching/index.html new file mode 100644 index 0000000..27667e3 --- /dev/null +++ b/presentations/coaching/index.html @@ -0,0 +1,260 @@ + + + + + + OpenTechSchool + + + + + + + + + + + + +
+

Coaching Guide

+

A short introduction to the way OpenTechSchool coaches learners

+
+ +
+ +
+
+
+

OpenTechSchool

+

Coaching Guide

+

opentechschool.org

+
+
+
+ +
+
+
+

What are we trying to do?

+
+

You are about to help out at an OpenTechSchool workshop as a coach. With this presentation we want to give you a quick introduction of what that means.

+

The focus for the event is to show learners that coding and tech is nothing to be afraid of, but rather a lot of fun!

+
+
+ +
+
+
+

Introduction to Coaching

+
+

This OTS coaching style has its roots in the RailsBridge teaching style. As such it is very focused on creating a friendly and open environment for learners of all sorts.

+

Achieving this and having a pleasant learning experience is the focus of this presentation.

+
+
+ +
+
+
+

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.

+

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

+
+

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

+

+

    +
  • Stand by on the sidelines
  • +
  • Are right there when needed
  • +
  • Focus on the learners
  • +
  • Have sympathy for their (in-)abilities
  • +
  • Encourage learners to go further through posititve motivation
  • +
  • And ensure they have fun doing it.
  • +
+

+
+
+ +
+
+
+

Creating a friendly environment

+
+

+

    +
  • Smile
  • +
  • Make eye contact
  • +
  • Admit when you don't know something
  • +
  • Be kind and friendly
  • +
  • Use their name (we all have name tags)
  • +
  • Tell learners it's ok to make mistakes
  • +
  • and to take breaks when it gets frustrating
  • +
+

+
+
+ +
+
+
+

Creating a friendly environment, part 2

+
+

+

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

+
+
+ +
+
+
+

Creating a friendly environment, part 3

+
+

+

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

+
+
+ +
+
+
+

Questions are good!

+
+

+

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

+
+
+ +
+
+
+

Responding to questions

+
+

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

    +
  • Positevly: +
      +
    • "I’m glad you asked that."
    • +
    • "What an interesting question!"
    • +
    • "Great question!"
    • +
    • "Hm, I'm not sure... Let's look in the Internet/ask someone else."
    • +
    +
  • +
  • If in doubt: blame the material, never the learner.
  • +
+

+
+
+ +
+
+
+

Pacing

+
+

+

    +
  • This is not about you, but about the learner. We go at their pace.
  • +
  • Everyone learns at their own pace. That's a good thing!
  • +
  • Talk sssssslllllloooooowwwwwwllllllyyyyyyyy.
  • +
  • Wait much longer than you feel is comfortable for questions/comments (count to 10 in your head)
  • +
+

+
+
+ +
+
+
+

Don'ts

+

a few things we are not doing

+
+
+
+ +
+
+
+

Don'ts

+
+

+

    +
  • We do not hit on anyone or make sexually suggestive remarks
  • +
  • We do not roll our eyes or laugh at questions
  • +
  • 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 discuss programming languages

+
+

Doing so confuses learners. In the tech community we have some strong opinions and our ways to express them, but for people new to it, this can quickly look like a huge fight. We do not fight each other! +

+

We are here to coach you in this programming language/method/technology and that is the focus for this event.

+
+
+ +
+
+
+

Thanks

+

for helping us spread the fun of coding

+
+
+
+ +
+ +
+ + + + + diff --git a/presentations/opencurriuculum-github-for-the-win/images/fork_network.png b/presentations/opencurriuculum-github-for-the-win/images/fork_network.png new file mode 100644 index 0000000..b0e41c6 Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/fork_network.png differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/github_fileview.png b/presentations/opencurriuculum-github-for-the-win/images/github_fileview.png new file mode 100644 index 0000000..d8a2bb2 Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/github_fileview.png differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/github_fileview_hl.png b/presentations/opencurriuculum-github-for-the-win/images/github_fileview_hl.png new file mode 100644 index 0000000..7b9fa91 Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/github_fileview_hl.png differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/issues.png b/presentations/opencurriuculum-github-for-the-win/images/issues.png new file mode 100644 index 0000000..0c6d33f Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/issues.png differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/issues_hl.png b/presentations/opencurriuculum-github-for-the-win/images/issues_hl.png new file mode 100644 index 0000000..7915fc3 Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/issues_hl.png differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/js_fab.jpg b/presentations/opencurriuculum-github-for-the-win/images/js_fab.jpg new file mode 100644 index 0000000..f5501ea Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/js_fab.jpg differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/js_fab_hl.jpg b/presentations/opencurriuculum-github-for-the-win/images/js_fab_hl.jpg new file mode 100644 index 0000000..6239f40 Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/js_fab_hl.jpg differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/macvim.png b/presentations/opencurriuculum-github-for-the-win/images/macvim.png new file mode 100644 index 0000000..ec2f481 Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/macvim.png differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/published_online.png b/presentations/opencurriuculum-github-for-the-win/images/published_online.png new file mode 100644 index 0000000..0e1e333 Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/published_online.png differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/published_online_hl.png b/presentations/opencurriuculum-github-for-the-win/images/published_online_hl.png new file mode 100644 index 0000000..9024f66 Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/published_online_hl.png differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/pull_request_fill.png b/presentations/opencurriuculum-github-for-the-win/images/pull_request_fill.png new file mode 100644 index 0000000..aa4b16f Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/pull_request_fill.png differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/pull_request_german.png b/presentations/opencurriuculum-github-for-the-win/images/pull_request_german.png new file mode 100644 index 0000000..17f44ae Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/pull_request_german.png differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/py_sthlm.jpg b/presentations/opencurriuculum-github-for-the-win/images/py_sthlm.jpg new file mode 100644 index 0000000..91ab695 Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/py_sthlm.jpg differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/py_sthlm_hl.jpg b/presentations/opencurriuculum-github-for-the-win/images/py_sthlm_hl.jpg new file mode 100644 index 0000000..dbe9a99 Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/py_sthlm_hl.jpg differ diff --git a/presentations/opencurriuculum-github-for-the-win/images/sublime.png b/presentations/opencurriuculum-github-for-the-win/images/sublime.png new file mode 100644 index 0000000..900a4f9 Binary files /dev/null and b/presentations/opencurriuculum-github-for-the-win/images/sublime.png differ diff --git a/presentations/opencurriuculum-github-for-the-win/index.html b/presentations/opencurriuculum-github-for-the-win/index.html new file mode 100644 index 0000000..00bd520 --- /dev/null +++ b/presentations/opencurriuculum-github-for-the-win/index.html @@ -0,0 +1,399 @@ + + + + + + OpenTechSchool + + + + + + + + + + + + +
+

OpenCurriculum

+

GitHub for the win

+
+ +
+ +
+
+
+

OpenTechSchool

+

OpenCurriculum

+

GitHub for the win

+
+
+
+ +
+
+
+

Two things about OpenTechSchool

+
+

OpenTechSchool is an initiative started in Berlin in April 2012, aimed at providing learning opportunities for people by organising hands-on coding- and tech-related workshops and meetups for learners.

+

Our focus is on empowering people by providing hands-on learning experiences in a open and safe environment, as well as enabling others to do the same by providing open documentation of our work. +

+
+
+ +
+
+
+

We are just the coaches

+

A short introduction to our most used learning model

+
+
+
+ +
+
+
+

Introduction to coaching

+
+

In OTS we do not teach, but rather coach. This means there is no one lecturing at the front of the room at our workshops. Instead, you work through the curriculum yourself at your own pace or in small groups of peers with more experienced people around to help you out whenever needed - we call them "the coaches on the sidelines."

+
+
+ +
+
+
+
+ +
+
+ + +
+
+
+
+ +
+
+ +
+
+
+
+ +
+
+ + +
+
+
+
+ +
+
+ +
+
+
+

New learning material needed

+
+

This learning style requires different learning materials than most of what is out there. And we -- as OpenTechSchool -- had some extra requirements:

+

+

    +
  • Easily written
  • +
  • Public and openly accessible
  • +
  • Easy to contribute to
  • +
  • Easy and cheap to host and maintain
  • +
+

+
+
+ +
+
+
+

Due to time constraints:

+

Let's use
GitHub-pages

+

Static HTML-pages with Git at their heart

+
+
+
+ +
+
+
+

Creating a bunch of possibilities

+
+

+

    +
  • Easy collaborative writing
  • +
  • Local but published and accessible changes via forking
  • +
  • Contributing via pull-requests (German version)
  • +
  • Published online quickly and there forever
  • +
+

+
+
+ +
+
+
+

Easy writing

+
+

+

    +
  • Writing simple markdown or restructured text files
  • +
  • Using well-established tools like Git and GitHub for collaboration
  • +
  • Everyone can use their favourite editor
  • +
+

+
+
+ +
+
+
+
+ +
+
+ +
+
+
+
+ +
+
+ +
+
+
+

Forking

+
+

+

    +
  • Make your own copy to work on
  • +
  • Share it online with others
  • +
  • Work with others on "not yet official" material
  • +
+

+
+
+ +
+
+
+
+ +
+
+ + +
+
+
+

Pull requests

+
+

Once your part is done, make a "pull request" to the main repository. It then gets merged into it with just a click.

+
+
+ +
+
+
+
+ +
+
+ +
+
+
+
+ +
+
+ +
+
+
+

Hosted online for free and forever

+
+

Just seconds after you've pushed your content, it is available online. There, it's hosted for free and forever.

+
+
+ +
+
+
+
+ +
+
+ +
+
+
+
+ +
+
+ + +
+
+
+

But there's more!

+
+
+
+ +
+
+
+
+ +
+
+ +
+
+
+
+ +
+
+ + +
+
+
+
+

Fixes on site

+
+

You can quickly fix the material during the workshop via the github online editor and ask the participants to hit refresh to distribute it, long before most of them will have noticed the mistake. Priceless!

+
+
+
+ +
+
+
+
+ +
+
+ +
+
+
+
+ +
+
+ + +
+
+
+
+

Tracking issues on site

+
+

You can also track your bugs directly while working with the learners online so that you don't forget to fix them later. Again: open and public.

+

So, everyone is free to fix the issues. Make a pull request and get stuff fixed.

+
+
+
+ + +
+
+
+

Conclusion

+
+
+
+ + +
+
+
+

Only plaintext is open

+
+

+

    +
  • Content is key
  • +
  • Rendering is secondary
  • +
  • WYSIWIGs suck
  • +
  • and are unportable
  • +
  • even Wordpress
  • +
  • and GoogleDocs
  • +
+

+
+
+ + +
+
+
+

But what about wikiX?

+
+

+ Wikis often suffer from bad design, both visually and structurally. For example, just think about organising learning material in "categories!" +

+

+ Wikis focus on speed. Quality comes second: first you publish, then someone reviews your work (or often doesn't). +

+

+ For learnering material, quality is more important than speed: only after having been reviewed by a peer, a pull-request gets merged and the content is published. +

+
+
+ +
+
+
+

Use GitHub

+

and plaintext pages for
managing your open content

+
+
+
+ + +
+
+
+

Thanks

+

is.gd/OTSwhyGithub

+
+
+
+ + +
+ + + + + diff --git a/theme/style.css b/theme/style.css index f4123c6..85811e4 100644 --- a/theme/style.css +++ b/theme/style.css @@ -109,6 +109,10 @@ h1, h2, h3 { color: #888; } +.slide .small { + font-size: 0.6em; +} + .slide b, .slide strong { font-weight: bold; @@ -230,8 +234,12 @@ h1, h2, h3 { } /* Cover */ -.slide.cover header { - color: #fff; +.slide.cover header, +.slide.shout a, +.slide.shout a:visited, +.slide.cover a, +.slide.cover a:visited { + color: #29f; } .slide.cover section { @@ -239,6 +247,7 @@ h1, h2, h3 { overflow: hidden; } + .slide.cover section:before { display: none; } @@ -274,21 +283,28 @@ h1, h2, h3 { transform: translateY(-50%); } + + /* Shout */ - +.slide.invert header, .slide.shout header, .slide.shout-louder header { color: #fff; - position: absolute; - top: 40%; - left: 0; width: 100%; - text-align: center; -webkit-transform: translateY(-50%); -moz-transform: translateY(-50%); -ms-transform: translateY(-50%); -o-transform: translateY(-50%); transform: translateY(-50%); + text-align: center; +} + +.slide.shout section > *:first-child, +.slide.centered section > *:first-child, +.slide.shout-louder section > *:first-child { + position: absolute; + top: 50%; + left: 0; } .slide.shout .tagline, @@ -311,6 +327,12 @@ h1, h2, h3 { background: #286d99; } +.slide.invert section { + background: #286d99; + color: #fff; +} + + .slide.shout-louder section { background: #E04C3E; }