🧑🏽‍🤝‍🧑🏽 day-plan

🔖
  1. Energiser
  2. Conflict Resolution
  3. MWT Workshop
  4. Morning break
  5. Study Group
  6. Lunch
  7. 🔍 Explore objects
  8. Afternoon break
  9. Code Review
  10. Study Group
  11. Code Review
  12. Retro

✍🏽 Register

Energiser

Every session begins with an energiser. Usually there’s a rota showing who will lead the energiser. We have some favourite games you can play if you are stuck.

  1. Traffic Jam: re-order the cars to unblock yourself
  2. Telephone: draw the words and write the pictures
  3. Popcorn show and tell: popcorn around the room and show one nearby object or something in your pocket or bag and explain what it means to you.

Conflict Resolution

Learning Objectives

Introduction

We will explore how to resolve conflicts and steps you can take to avoid them in the first place.

Why do we disagree?

🎯 Goal: Identify reasons for disagreement (20 minutes)

Working in a group of 3 - 5 people for 10 minutes, please discuss the questions below.

  • Make a list of reasons why technical people might disagree at work.
  • What is a team?
  • Where is the boundary between a disagreement and a conflict?

Feed back your conclusions to the room and briefly discuss (10 minutes).

Practice resolving conflicts

🎯 Goal: Role-play a conflict based on different goals (30 minutes)

  • Work in groups of three. Assign yourselves as person A, B or C.
  • Pretend you are planning a holiday together. 
    • Person A wants the most outdoor adventure they can
    • person B wants to save money
    • person C wants cultural and social experiences
  • Prepare by yourself (1 minute):
    • Plan the ideal holiday from your role’s perspective.
    • Identify some parts of your plan that you will not compromise.
  • Negotiate and agree on a shared plan (10 minutes).
    • Try to resolve conflicts that arise.
  • Feed back to the whole room (10 minutes). 
    • Explain techniques you used to reach an agreement.

MWT Workshop

Most Wanted Topics 🔥

Great news! After gathering your feedback from past retros, we’re officially incorporating a new element into the curriculum!

Your instructor will soon share a link to the RetroTool board. There, you can post stickers on topics you’re finding challenging. The topic with the most votes will be the focus of our workshop! If time allows, we’ll dive into the 2nd, 3rd and even more voted topics.

Don’t forget to take short break 🧘‍♂️ during the session happy coding!

Use this time wisely 🎯

To make the most out of this workshop and ensure you’re getting the best value, here are a few tips to keep in mind that will help you stay focused, collaborate effectively, and leave with actionable insights:

  • Come Prepared: Come Prepared beforehand and gather your thoughts on the specific areas where you need clarification or support. This ensures you ask targeted questions during the workshop.

  • Engage Actively: Don’t just observe ask questions, share your experiences, and participate in discussions. Workshops are most valuable when everyone collaborates.

  • Collaborate with Peers: If you see a fellow participant struggling with a topic you’re comfortable with, offer your help. Peer learning enhances the overall experience for everyone.

  • Apply Immediately: After the workshop, try to implement what you’ve learned in your course work or personal projects. Practical application reinforces your learning.

  • Follow-Up: If a topic wasn’t fully covered or you still have doubts, follow up with your instructor or peers after the session. This ensures no questions are left unanswered.

Morning Break

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

Study Group

Learning Objectives

What are we doing now?

You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.

Use this time wisely

You will have study time in almost every class day. Don’t waste it. Use it to:

  • work through the coursework
  • ask questions and get unblocked
  • give and receive code review
  • work on your portfolio
  • develop your own projects

Lunch

Take your lunch break and be back in an hour!

🔍 Explore objects 🔗

Instructions

This workshop aims to check your understanding.

Each task will explain whether or not you should run the code.

For each task, you can use Data Groups Sprint 2 prep
to help you with the questions.
You can also use documentation to look up any functions that are unfamiliar.
Don’t use ChatGPT or any other AI tool to help you.

🧰 Setup

  1. Get into pairs or groups of up to three.
  2. Make sure you have a clone of the CYF-Workshops repository on your local machine

This workshop can be found here 👉 https://github.com/CodeYourFuture/CYF-Workshops/tree/main/objects
In this workshop, each file contains a different problem at a particular level.

You should start this project at Level 100 and then move through the levels in ascending order, level 200, 300 etc.

➡️ Go to Level 100

Afternoon Break

Take your short afternoon break and be back in 15 minutes!

🛎️ Code waiting for review 🔗

Below are trainee coursework Pull Requests that need to be reviewed by volunteers.

MC-JUL-24 | Umair Riaz | Module JS 2 | Week 2 🔗

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review
MC-JUL-24 | Umair Riaz | Module JS 2 | Week 1 🔗

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review
Migracode|Afere Onome Precious|Module Js-2|Sprint 4|To-do list 🔗

Learners, PR Template

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review
Migracode Barcelona|Afere Precious Onome|Module JS 2 Sprint 4|Slide-Show 🔗

Learners, PR Template

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review
Ebtesan Ahmed | JS2 | Slideshow 🔗

Learners, PR Template

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review
See more pull requests

Study Group

Learning Objectives

What are we doing now?

You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.

Use this time wisely

You will have study time in almost every class day. Don’t waste it. Use it to:

  • work through the coursework
  • ask questions and get unblocked
  • give and receive code review
  • work on your portfolio
  • develop your own projects

🛎️ Code waiting for review 🔗

Below are trainee coursework Pull Requests that need to be reviewed by volunteers.

MC-JUL-24 | Umair Riaz | Module JS 2 | Week 2 🔗

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review
MC-JUL-24 | Umair Riaz | Module JS 2 | Week 1 🔗

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review
Migracode|Afere Onome Precious|Module Js-2|Sprint 4|To-do list 🔗

Learners, PR Template

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review
Migracode Barcelona|Afere Precious Onome|Module JS 2 Sprint 4|Slide-Show 🔗

Learners, PR Template

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review
Ebtesan Ahmed | JS2 | Slideshow 🔗

Learners, PR Template

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review
See more pull requests

Retro: Start / Stop / Continue

  Retro (20 minutes)</span>

A retro is a chance to reflect. You can do this on RetroTool (create a free anonymous retro and share the link with the class) or on sticky notes on a wall.

  1. Set a timer for 5 minutes. There’s one on the RetroTool too.
  2. Write down as many things as you can think of that you’d like to start, stop, and continue doing next sprint.
  3. Write one point per note and keep it short.
  4. When the timer goes off, one person should set a timer for 1 minute and group the notes into themes.
  5. Next, set a timer for 2 minutes and all vote on the most important themes by adding a dot or a +1 to the note.
  6. Finally, set a timer for 8 minutes and all discuss the top three themes.