🧑🏾‍🤝‍🧑🏾 day-plan

🔖
  1. Energiser
  2. Demo
  3. Morning break
  4. Solo project
  5. Development
  6. lunch
  7. Development
  8. Afternoon break
  9. Development
  10. Wrap

✍🏽 Register

Wemoji

Learning Objectives

😀😢😲

This game can be played in-person or online with 2 or more participants.

One person will be the “Emoter” and the others will be “Empaths.”

  1. Emoter, choose a random emoji from the list.
  2. Emoter, act out the emoji using only facial expressions and body language (no sounds or words).
  3. Empaths, try to guess the emoji.
  4. The first Empath to correctly identify the emoji becomes the next Emoter.
Emojis List

❤️ Red Heart 😭 Loudly Crying Face 💀 Skull 🔥 Fire 🫶 Heart Hands ✅ Check Mark Button ✨ Sparkles 😂 Face with Tears of Joy 😊 Smiling Face with Smiling Eyes ⭐ Star 🥹 Face Holding Back Tears 🫡 Saluting Face 🙏 Folded Hands 🤍 White Heart 👀 Eyes 🫶🏻 Heart Hands 🫂 People Hugging 🩷 Pink Heart 🫠 Melting Face ❤️‍🩹 Mending Heart ✔️ Check Mark 😍 Smiling Face with Heart-Eyes 🦴 Bone 🗿 Moai 👍 Thumbs Up ❤️‍🔥 Heart on Fire 😔 Pensive Face 🫵 Index Pointing at the Viewer 👑 Crown

~ From emojipedia Most Popular Emojis 2024

Facilitator Check in questions

Guide participants to reflect on emotional expression and recognition
  • What was most challenging about expressing without words?
  • Which emoji were easiest to express, or read? Which were most difficult?
  • How does this exercise relate to reading people in real-life situations?

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.

Solo project 🔗

Welcome to The Piscine

In this repo there are three projects:

  • Sprint 1 Group Project
  • Sprint 2 Group Project
  • Sprint 3 Solo Project

In each project folder you will find a readme with the project requirements and any setup files.

Solo Development

Learning Objectives

This time is set aside for you to make progress on your solo project. But remember, you are not alone! You have your mentors and peers to help you. Here are some strategies to help you work effectively:

👤 User stories

As a [who], I can [what] so that [why]

Spend some time working on your initial user stories 🧶 🧶 user stories A user story is a short sentence stating some goal a user can expect to achieve when using the product we are building. . Write them as tickets on your planning board.

  1. Identify described requirements: What are the requirements of your project? What are the features you need to build? Describe them in user story format.
  2. Create a strategy: How will you implement these user stories? What are the steps you need to take to complete them? Update your tickets with this information.
  3. Express as test cases: How will you know when you have completed the user story? What tests can you write to verify that the user story is complete? Write these tests.

Use this opportunity to compare your user stories with others and ask for feedback in real time. 🌟 Everyone will approach the project differently, and you can get feedback to test your ideas.

🍅 Pomodoro

Each person take a small-scoped ticket. Set a timer for . Use this focused time to complete your ticket and open a PR.

⌛ Time’s up! Take a break! Make a cup of tea. Walk around a bit.

Now set a new and review each PR as a group.

⌛ Time’s up! Take a break! Make a cup of tea. Stretch! Look at how much progress you made in one hour. ✨

🚧 Blockers

Identify any blockers or dependencies in your project. What must be done first? What can be “decoupled” and done in any order? What parts will you need to research or ask for help from others? What parts are you confident about? Mark these on your board.

Describe your blocker

Describing the problem systematically will take you most of the way to resolving the blocker. Use the following template on a ticket on your board:

  1. What you did: Describe what you have done so far. Give links and code snippets.
  2. What you expected: Describe what you expected to happen.
  3. What actually happened: Describe what actually happened.

Blockers can feel frustrating, but in reality they are opportunities to explore and solve problems. This is what engineering is all about. 🌱

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.

Solo Development

Learning Objectives

This time is set aside for you to make progress on your solo project. But remember, you are not alone! You have your mentors and peers to help you. Here are some strategies to help you work effectively:

👤 User stories

As a [who], I can [what] so that [why]

Spend some time working on your initial user stories 🧶 🧶 user stories A user story is a short sentence stating some goal a user can expect to achieve when using the product we are building. . Write them as tickets on your planning board.

  1. Identify described requirements: What are the requirements of your project? What are the features you need to build? Describe them in user story format.
  2. Create a strategy: How will you implement these user stories? What are the steps you need to take to complete them? Update your tickets with this information.
  3. Express as test cases: How will you know when you have completed the user story? What tests can you write to verify that the user story is complete? Write these tests.

Use this opportunity to compare your user stories with others and ask for feedback in real time. 🌟 Everyone will approach the project differently, and you can get feedback to test your ideas.

🍅 Pomodoro

Each person take a small-scoped ticket. Set a timer for . Use this focused time to complete your ticket and open a PR.

⌛ Time’s up! Take a break! Make a cup of tea. Walk around a bit.

Now set a new and review each PR as a group.

⌛ Time’s up! Take a break! Make a cup of tea. Stretch! Look at how much progress you made in one hour. ✨

🚧 Blockers

Identify any blockers or dependencies in your project. What must be done first? What can be “decoupled” and done in any order? What parts will you need to research or ask for help from others? What parts are you confident about? Mark these on your board.

Describe your blocker

Describing the problem systematically will take you most of the way to resolving the blocker. Use the following template on a ticket on your board:

  1. What you did: Describe what you have done so far. Give links and code snippets.
  2. What you expected: Describe what you expected to happen.
  3. What actually happened: Describe what actually happened.

Blockers can feel frustrating, but in reality they are opportunities to explore and solve problems. This is what engineering is all about. 🌱

Afternoon Break

Please feel comfortable and welcome to pray at this time if this is part of your religion.

If you are breastfeeding and would like a private space, please let us know.

Solo Development

Learning Objectives

This time is set aside for you to make progress on your solo project. But remember, you are not alone! You have your mentors and peers to help you. Here are some strategies to help you work effectively:

👤 User stories

As a [who], I can [what] so that [why]

Spend some time working on your initial user stories 🧶 🧶 user stories A user story is a short sentence stating some goal a user can expect to achieve when using the product we are building. . Write them as tickets on your planning board.

  1. Identify described requirements: What are the requirements of your project? What are the features you need to build? Describe them in user story format.
  2. Create a strategy: How will you implement these user stories? What are the steps you need to take to complete them? Update your tickets with this information.
  3. Express as test cases: How will you know when you have completed the user story? What tests can you write to verify that the user story is complete? Write these tests.

Use this opportunity to compare your user stories with others and ask for feedback in real time. 🌟 Everyone will approach the project differently, and you can get feedback to test your ideas.

🍅 Pomodoro

Each person take a small-scoped ticket. Set a timer for . Use this focused time to complete your ticket and open a PR.

⌛ Time’s up! Take a break! Make a cup of tea. Walk around a bit.

Now set a new and review each PR as a group.

⌛ Time’s up! Take a break! Make a cup of tea. Stretch! Look at how much progress you made in one hour. ✨

🚧 Blockers

Identify any blockers or dependencies in your project. What must be done first? What can be “decoupled” and done in any order? What parts will you need to research or ask for help from others? What parts are you confident about? Mark these on your board.

Describe your blocker

Describing the problem systematically will take you most of the way to resolving the blocker. Use the following template on a ticket on your board:

  1. What you did: Describe what you have done so far. Give links and code snippets.
  2. What you expected: Describe what you expected to happen.
  3. What actually happened: Describe what actually happened.

Blockers can feel frustrating, but in reality they are opportunities to explore and solve problems. This is what engineering is all about. 🌱

Wrap

You are done for the day. Take a moment to reflect on what you have learned and achieved.

Stand in a circle and share:

  • 📛 your name
  • 💪🏽 one thing you built today
  • 👷🏾 the task you are going to work on next
  • 🛟 one thing you need help with

Give yourselves a round of applause. Now you have earned your rest. Usually people go for a drink (or a coffee) after class. You are welcome to join and wind down together.