🧑🏾‍🤝‍🧑🏾 day-plan

🔖
  1. Energiser
  2. Demo
  3. Morning break
  4. Interviews
  5. lunch
  6. Wrap Party

✍🏽 Register

Fizz Buzz

Learning Objectives

🔢 Fizz Buzz Gameplay

Arrange participants in a circle (either in-person or virtually). The game can be played with any number of people, but 5 or more is ideal.

Starting with 1, players count upwards in turn. However:

  • If a number is divisible by 3, say “Fizz” instead of the number
  • If a number is divisible by 5, say “Buzz” instead of the number
  • If a number is divisible by both 3 and 5, say “Fizz Buzz”

For example: 1, 2, Fizz, 4, Buzz, Fizz, 7, 8, Fizz, Buzz, 11, Fizz, 13, 14, Fizz Buzz, 16…

If a player makes a mistake, they’re out. Continue counting until only one player remains.

Set a timer for minutes per round. If you have time, play multiple rounds.

Facilitator Check in questions

Guide participants to reflect on the game and its implications
  • What strategies did you use to keep track of the numbers?
  • How did the pressure of quick responses affect your thinking?
  • Did you find yourself anticipating your turn? How many numbers ahead?
  • How does this game relate to problem-solving in programming?
  • What was most challenging: remembering the rules, doing the math, or staying focused?
  • How did the group’s energy change as the numbers got higher?
  • Can you think of any real-world scenarios where this kind of quick pattern recognition would be useful?

Evolve the game

Introduce variations to increase complexity and challenge
  • Round 2: Add “Fuzz” for numbers divisible by 7
  • Round 3: Replace “Fizz” with a clap, “Buzz” with a snap, and “Fizz Buzz” with a stomp
  • Round 4: Count backwards from 100, applying the same rules
  • Round 5: Allow players to create one new rule at the start of the round (e.g., “Bazz” for numbers ending in 2)

More resources

Demo

Learning Objectives

At CYF we expect you to demo your work to the class. You must have many opportunities to practice how to clearly and simply explain your work to others. This is really important for interviews and career success.

⏰ Timekeeper

The timekeeper will keep the groups on track.

Split randomly into groups of no more than 4 people. Mix up your teams. Each person will have 2 minutes to demo their work to the group. After the demo, the group will ask questions or give feedback for 5 minutes. Then the next person will demo their work.

🧑🏼‍🎓 Trainees

1. Demo

You will demo something about your work to the group.

You will have 2 minutes to explain what you did and why. It’s ok to show broken code or code that doesn’t work yet. Just make sure your demo is interesting.

2. Feedback

After the demo, the group will give you feedback for up to 5 minutes. It’s smart to suggest what kind of feedback you want by asking some “generative” questions. For example:

  • I wasn’t sure if it makes sense to try X. What do you think?
  • I liked the way I did X, but I know there are other approaches, what did you do?
  • I found X really confusing, did anyone else have the same problem?

💡 Tips:

  • Practice the format of demos before class.
  • Keep it simple. Don’t try to show everything you did. Just show one interesting thing.
  • Keep it short. Two minutes is enough.
  • Explain what you did and why.
  • Show your code.
  • Ask for feedback.

Morning Break

A quick break of fifteen minutes so we can all concentrate on the next piece of work.

Interviews

Learning Objectives

You will be asked to join a video call for your technical interview. We use an interview platform called Evidenced.

What to expect

  • The interview will be 15 minutes long
  • You will be asked to discuss a feature from a project you have worked on during the Piscine.
  • You may have written this feature yourself, or it may have been written by someone else in your group.

What questions will I be asked?

  • You will be asked to explain the code. You may be asked to:
  1. Play computer and run the code in your head
  2. Explain what the state of the application is at different points in the code
  3. Define the function and meaning of different parts of the code
  4. Refactor the code to meet new requirements given by the interviewer

Your interview will be recorded and scored against a rubric you can read before the interview. You will get the transcript of your interview with the decision about your application.

Once your interview is done, you are done. Join the wrap party and celebrate your hard work! What a journey! 🎉

Community Lunch

Every Saturday we cook and eat together. We share our food and our stories. We learn about each other and the world. We build community.

This is everyone’s responsibility, so help with what is needed to make this happen, for example, organising the food, setting up the table, washing up, tidying up, etc. You can do something different every week. You don’t need to be constantly responsible for the same task.

Wrap Party

You made it! 🎉

Thank you so much for your hard work. We will send you the results of your interview by email by the end of the week.

Now, join the wrap party and celebrate your achievements with your community. 🎈

Can you bring a snack or drink to share? 🍪🥤 Or a board game? We love Dixit, Codenames, and Rush Hour in particular.