Coordinator Guide

codebar workshops are a team effort and we really appreciate you wanting to help run things smoother! Here are some tips on how you can help:

  • Try to get to the event a little early: 10 minutes or so before the listed start time.

  • Be friendly, positive, and encouraging.

  • Try to be close at hand to the front desk where people are being checked in. This is so you are close by to give inductions and help with any required tasks. Once you’ve finished an induction or helping with something, head back to the front desk.

  • Try not to get caught up in conversations unless there are no more inductions or the organisers don’t need your help anymore.

  • Keep an eye for people who are on their own. Talk to them and introduce them to other people.

  • If you spot someone without a name badge, chances are they’re not checked in. Send them over to the front desk.

  • If someone comes to you with a complaint or a concern that you don’t know how to address, remember that the rest of the organisers and coordinators have your back and you can always ask for help.

Coach inductions

  1. Have they read the Code of Conduct?

  2. Have they read the Coach Guide?
    • If not, they should do so right now.
  3. How did they hear about codebar? What made them want to come along?

  4. Stress that we discourage the coaches from using their laptops. They are there to watch and guide, people are sometimes hesitant to ask a lot of questions.

  5. Explain that our goal is to guide students, answer their questions, help them learn how to tackle problems and to encourage them.

  6. If they are working with a group and are finding it hard (as the students might work at a different pace or need more attention) they should let us know and we will try to find someone to help out.

  7. If they need any help or have any concerns, they should speak to a coordinator or organiser.

  8. If they feel uncomfortable with someone’s behaviour, they should bring it to the attention of one of the organisers. It is very important to us that everyone feels safe and comfortable.

  9. Thank them for coming. We appreciate their help and any feedback that they may have, as without them we wouldn’t be able to have codebar! Let them know that they can get in contact with us at the local chapter’s mailing list (e.g. brighton@codebar.io).

  10. Encourage them to come to the social gathering afterwards, which is a great way to meet new people. They should come.

Student inductions

  1. Have they read the Code of Conduct?

  2. How did they hear about codebar? What made them want to come along?

  3. Have they done any development before?
    • If yes, what was that? Do they have a goal in mind? (e.g. Are they trying to build their own web app or a portfolio?)`
  4. Are you a student? Speak to them about your experience and how programming has changed things for you.

  5. Typing can be hard, but it’s very important when learning to code. Type everything and DO NOT copy and paste.

  6. codebar is not just about learning to code but also about making friends and meeting people with similar goals. Encourage them to chat to other people and come to the social gathering afterwards.

  7. If they need any help they should look for a coordinator or organiser.

  8. If they feel uncomfortable with someone’s behaviour, they should bring it to the attention of one of the organisers. It is very important to us to ensure that everyone feels safe and comfortable.