Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Better Together

Better Together

A roadmap to help the CoderDojo organization, the dojos, the mentors and the students work better together.

Avatar for Cameron McEfee

Cameron McEfee

April 13, 2013
Tweet

Other Decks in Education

Transcript

  1. I hate friction • Make it easier for you to

    do your job • Build tools • Reduce clutter
  2. Starting a dojo is scary • Where do I find

    a venue? • Where do I find mentors? • Where do I get lessons? • What do I do first?
  3. Running a dojo is a challenge • Dear GitHub: How

    do you run your dojo? • Dear GitHub: Can I come watch how your dojo runs? • Dear GitHub: Is there a mentor mailing list? • Dear GitHub: Is there a collection of lessons somewhere?
  4. Bad things • Too much information • Open ended instructions

    • CoderDojo provides suggestions, but not support
  5. 1 simple jumpstart guide • 1 format • 1 version

    • Easy, concise steps to follow • Realistic expectations
  6. coderdojo.com/setup • Automatic setup of all technology to run a

    dojo • Click checkboxes next to things you want • Automatically deploys everything to Heroku for you
  7. Automate events • Event creation • Ticket distribution • Mentor

    management • Student management (COPPA compliant)
  8. Frontend for each dojo • Each dojo has one •

    Home page: this session’s lesson • Kids only ever go to one url • Past lessons index • Backend built on the GitHub API (more on that later)
  9. • Helps coders work together • Designed with code and

    collaboration in mind • Version control, issue tracking, wikis, free websites GitHub.com
  10. This isn’t a sales pitch • Free bronze organization accounts

    for all dojos • 10 private repos • Unlimited public repos • Unlimited teams
  11. How to get yours 1. Create a GitHub organization for

    your dojo 2. Email [email protected] 3. Request a free CoderDojo organization coupon 4. Provide proof (CoderDojo email, photo of your face on the site, etc.)
  12. Lesson Plans repo • Create issues for each session date

    • Assign teachers • Discuss lesson topics before • Discuss results after • Historical data for future conversations
  13. Lesson Template repo • Consistent lesson flow • Consistent lesson

    format • More time on the lesson, less on formatting
  14. Lessons in individual repos • Based on the lesson template

    • Lesson in the readme.md • Include a license
  15. Private mentor tickets repo • Add mentors as collaborators to

    the repo • Prove they exist on the internet • Have lunch with them before adding them. No creeps. • Post ticket links in issues labeled with the session date • Mentors can manage their subscription settings through GitHub
  16. Use teams • Mentors team, parents team, organizers team •

    Organize mentors of similar skills into teams • Team mentions: “Ask @CoderDojoSF/javascript if they have input”
  17. Dress the part • Don’t look like a teacher. Teachers

    teach at you. • Dress like a peer. Mentors share knowledge. • Don’t force it. It’s not about being cool. It’s about not being superior.
  18. Mentor at eye level • Kneel next to the person

    you’re mentoring. • Eye level means you are peers. • Don’t teach. Share knowledge.
  19. Stand up • Each person that is one person away

    from you is one “hop” away. • Shake hands with everyone that is one “hop” away.
  20. You are all computers • You each have an IP

    address. • You can only communicate with people one “hop” away from you. • You can ask “Do you know where {IP} is?” • You can say “I know where {IP} is.” • You can say “I know someone who knows where {IP} is.” • You have to keep quiet so we don’t hear you.
  21. I’m looking for {IP} • I’ll ask people one “hop”

    away from me if they know where {IP} is. • You ask people one “hop” from you. • If you are it, don’t shout it out. Tell it to people one “hop” away.
  22. We found {IP}! • I’ve got a message (hint: it’s

    a sticker). • I’m going to send my message to the person one hop away from me that knows where {IP} is.