Slide 1

Slide 1 text

Beer Together

Slide 2

Slide 2 text

@cameronmcefee I reduce friction at GitHub.

Slide 3

Slide 3 text

I hate friction • Make it easier for you to do your job • Build tools • Reduce clutter

Slide 4

Slide 4 text

GitHub has a simple goal Make it easier to work together than alone

Slide 5

Slide 5 text

US dojos operate alone

Slide 6

Slide 6 text

CoderDojo has a lot of friction

Slide 7

Slide 7 text

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?

Slide 8

Slide 8 text

CoderDojo.com is confusing • Five start-up guides • Three sites

Slide 9

Slide 9 text

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?

Slide 10

Slide 10 text

Observations

Slide 11

Slide 11 text

Good things • Lots of info • Lots of experience • Lots of resources

Slide 12

Slide 12 text

Bad things • Too much information • Open ended instructions • CoderDojo provides suggestions, but not support

Slide 13

Slide 13 text

The message this sends?

Slide 14

Slide 14 text

This is my dojo There are many like it, but I’m all alone

Slide 15

Slide 15 text

What can we do?

Slide 16

Slide 16 text

Create dojos, together

Slide 17

Slide 17 text

This is my dream

Slide 18

Slide 18 text

1 simple jumpstart guide • 1 format • 1 version • Easy, concise steps to follow • Realistic expectations

Slide 19

Slide 19 text

Open source almost everything Mentors, parents, anyone can fix and improve things

Slide 20

Slide 20 text

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

Slide 21

Slide 21 text

Automate events • Event creation • Ticket distribution • Mentor management • Student management (COPPA compliant)

Slide 22

Slide 22 text

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)

Slide 23

Slide 23 text

Duh, we already have that ORLY? How should I know?

Slide 24

Slide 24 text

Dojo communication • Mailing list • Newsletter • Important things, not every thing

Slide 25

Slide 25 text

Mentor mentor “Starting a dojo? Ask me anything. Think of me as your mentor mentor”

Slide 26

Slide 26 text

You start a dojo CoderDojo starts it with you

Slide 27

Slide 27 text

Run dojos, together

Slide 28

Slide 28 text

• Helps coders work together • Designed with code and collaboration in mind • Version control, issue tracking, wikis, free websites GitHub.com

Slide 29

Slide 29 text

This isn’t a sales pitch • Free bronze organization accounts for all dojos • 10 private repos • Unlimited public repos • Unlimited teams

Slide 30

Slide 30 text

How to get yours 1. Create a GitHub organization for your dojo 2. Email support@github.com 3. Request a free CoderDojo organization coupon 4. Provide proof (CoderDojo email, photo of your face on the site, etc.)

Slide 31

Slide 31 text

Now what? This is how GitHub runs our dojo

Slide 32

Slide 32 text

Lesson Plans repo • Create issues for each session date • Assign teachers • Discuss lesson topics before • Discuss results after • Historical data for future conversations

Slide 33

Slide 33 text

Lesson Template repo • Consistent lesson flow • Consistent lesson format • More time on the lesson, less on formatting

Slide 34

Slide 34 text

Lessons in individual repos • Based on the lesson template • Lesson in the readme.md • Include a license

Slide 35

Slide 35 text

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

Slide 36

Slide 36 text

Use teams • Mentors team, parents team, organizers team • Organize mentors of similar skills into teams • Team mentions: “Ask @CoderDojoSF/javascript if they have input”

Slide 37

Slide 37 text

speakerdeck.com Share slides

Slide 38

Slide 38 text

Share knowledge, together

Slide 39

Slide 39 text

Teaching: What you think is important

Slide 40

Slide 40 text

Mentoring: What they think is important

Slide 41

Slide 41 text

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.

Slide 42

Slide 42 text

Mentor at eye level • Kneel next to the person you’re mentoring. • Eye level means you are peers. • Don’t teach. Share knowledge.

Slide 43

Slide 43 text

Learn, together

Slide 44

Slide 44 text

Learning together is important

Slide 45

Slide 45 text

Let’s learn about networks

Slide 46

Slide 46 text

Stand up • Each person that is one person away from you is one “hop” away. • Shake hands with everyone that is one “hop” away.

Slide 47

Slide 47 text

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.

Slide 48

Slide 48 text

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.

Slide 49

Slide 49 text

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.

Slide 50

Slide 50 text

Enjoy your sticker, {IP}

Slide 51

Slide 51 text

Beer Together

Slide 52

Slide 52 text

Thank you You are no longer alone