Becoming a Coach
You heard about the Rails Girls Summer of Code and want to be a coach? Here you’ll find all you need to know about what coaching actually means.
- What it takes to be a coach
- Why should I be a coach?
- What does coaching require?
- How much time does coaching take?
- Ways to find a team and register as a coach
What it takes to be a coach
First of all, coaches are patient, tolerant and open people! Ideally, they have some experience in coaching already - either from a Rails Girls event or something similar like a local workshop.
For your students, learning the process will be more important than learning the tools; whatever gets them started, curious and eager to learn is a perfect tool, no matter your personal preferences. Keep in mind that your preferences – just like the "common knowledge of the community" – are the result of a long, long learning process which you, and the community, have gone through. Give your students the same chance to discover. Our goal is to get people started, learning and staying excited about coding!
Why should I be a coach?
There are a lot of good reasons to become a coach. First and foremost, you will be giving back to the community for a great cause: by empowering women to contribute to open source. It's a great way to share your knowledge. We also believe that coaching can be really rewarding for your own work, that it can improve the way you write code and help you grow as a developer, as well as make you think about concepts you take for granted. And above all, we promise you an overwhelming buzz looking into the happy faces of your students when they succeed.
What does coaching require?
During the application process, we suggest that the coaches help their team with the project plan. This involves setting up a milestone-driven plan and "stretch goals" for the summer, keeping in mind that requirements and goals might change throughout the program.
It is important for coaches to teach the process of programming - showing the way to a solution rather than telling the answer. This will sometimes include going over the basics, showing how to debug and troubleshoot, or discussing concepts on paper. Coaches should spend time with their students in front of the screen, guiding them through the relevant coding steps (eg. by asking mindful questions). Every project is different; just make sure your students really understand what you are trying to teach them, at the risk of not being DRY :)
How much time does coaching take?
During the application period (March 2015) a few hours a week.
During the period of the Summer of Code (July-September 2015), we recommend around 1-2 hours a day of personal time plus chat or email.
Coaches are not expected to work together with their students full-time! But from a student's perspective, as they will constantly run into problems they need help with, it is best for them and their progress if they have a coach at hand most of the time, which is why we recommend that coaching be shared between a few coaches.
We also encourage you to ask your company to become a Coaching Company.
Ways to find a team and register as a coach
As a first step you can register yourself as a coach here: teams.railsgirlssummerofcode.org/.
If you don't know any students yet, reach out to your local Rails Girls chapter. There you can get to know students and other coaches. We also recommend reaching out to local developer and Ruby user groups, as well as study groups (if there are any in your area).
We also have a Rails Girls Summer of Code community mailing list: send an email introducing yourself and offering to become a coach. Additionally, you can spread the word on Twitter mentioning @RailsGirlsSoC and we'll retweet and help you connect to students.
If you have any further questions, drop us a line at firstname.lastname@example.org.