RailsGirls teaches people to code, so we are sat at tables with computers. You’ll have to split groups, namely: who will sit at the same table?

Sit one mentor at every table, and be very clear that everyone can change tables: this will allow people not to feel shame if they are uncomfortable with anyone, or if they feel pressured into learning a specific topic they don’t like.

— — —

Many events will try to separate based on previous experience, which looks like an easy solution, and works quite well (I don’t judge), but I found quite difficult to get the right mix. Some key questions are:

• knows programming or never programmed
• knows the Web stack (HTML/CSS/basic JS) or not
• knows MVC (in any lang/framework) or not

How would a “true beginner” compare to an advanced WordPress tweaker, a systems C programmer, a PHP-without-framework developer?

— — —

So I try to split by interests, and I found it helped foster a feeling of bonding and sharing: “we’re here for the same reason, and if you teach me things you already know I hope I can bring my perspective from another point of view”.

My four categories are:

• “I want to understand what the hell my coworkers are talking about”
• “I have some app from friends or freelancers or agency and want to regain control of it but just touch the design”
• same as above but backend-only
• “I want to become full-fledged developers”

Yes, you’ll notice it could be very close to “what is your context, who are the people around you right now or in very short-term future, and what do/will they need?”.

Because teaching people is helping them help others, and everyone be awesome :)