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.

Traffic Jam: re-order the cars to unblock yourself
Telephone: draw the words and write the pictures
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.

Learning Objectives

Introduce and welcome new volunteers
Nominate a timekeeper
Check the morning day plan and group structures

Planning during the week

🧭 During the week, create a post on Slack and get some people to take on the roles of facilitator and timekeeper. Nominate new people each time.

👣 Steps

If you haven’t done so already, choose someone (volunteer or trainee) to be the facilitator for this morning orientation block. Choose another to be the timekeeper.

🎙️ The Facilitator will:

Assemble the entire group (all volunteers & all trainees) in a circle
Briefly welcome everyone with an announcement, like this:
💬 “Morning everyone, Welcome to CYF {REGION}, this week we are working on {MODULE} {SPRINT} and we’re currently working on {SUMMARISE THE TOPICS OF THE WEEK}”
Ask any newcomers to introduce themselves to the group, and welcome them.
Now check: is it the start of a new module? Is it sprint 1? If so, read out the success criteria for the new module.
Next go through the morning day plan only (typically on the curriculum website) - and check the following things:

Facilitator Checklist

Check the number of volunteers you have for the morning
Check someone is leading each session
Describe how any new activities works for the group
Decide how best to allocate trainees and volunteers for a given block - most blocks will make this clear

⏰ The Timekeeper will:

Announce the start of an activity and how long it will take (check everyone is listening)
Manage any whole class timers that are used in an activity
Give people a 10-minute wrap-up warning before the end of an activity
Announce the end of an activity and what happens next

Link to the coursework

https://curriculum.codeyourfuture.io/js3/success/

Why are we doing this?

🔑 The most important thing is that you are secure in your understanding.

At the end of the course, we will expect you to build novel applications using your understanding. If you cannot build things, we cannot put you forward for jobs. It is in your personal interest to make sure you have properly understood this module.

To progress to the next module you need to meet the success criteria for this module. How will you as a cohort meet the module success criteria? Discuss it in your class channel and make a plan together.

Strategies

🧑🏿‍🎤 good strategies

asking volunteers to review your code
helping each other with coursework blockers
arranging midweek study sessions
using Saturday time to review code and cohort tracker

🙅🏿 bad strategies

opening empty PRs
copying and pasting
breaking the Trainee Agreement
mistaking the measure for the target

Maximum time in hours

.5

How to get help

Discuss with your cohort. Support each other.

How to submit

In week 4 of your module you will need a representative to report to the organisation. Here’s your template, fill in your details, delete as appropriate, and post it on your cohort channel on Slack:

Progress Template

📈 Cohort Progress Report from @cohort-name to @programme-team

criterion
criterion
criterion
criterion

✅ We are progressing to the next module.
⛔ We are taking a consolidation week to meet our targets.

🎯 Topic Code Review
🎯 Topic Communication
🎯 Topic Delivery
🎯 Topic Requirements
🎯 Topic Teamwork
🎯 Topic Time Management
🏕 Priority Mandatory
🦔 Size Tiny
🎯 Topic Testing
📅 JS3
📅 Week 1
📅 Week 4

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.

Add recommended VS Code extensions 🔗

What does this change?

This PR introduces a curated list of recommended Visual Studio Code extensions to the module. The aim is to standardize the development environment for all trainees, ensuring they have access to essential tools and features that enhance their learning experience, and save our mentors’ time and energy.

Common Content?

This change does not directly modify the common content shared across modules but provides an essential resource that complements the existing curriculum. It ensures that all trainees, regardless of their module, have a consistent set of tools at their disposal.

Block/s

Common Theme?

Yes

Issue number: #368

Org Content?

Module

Checklist

I have read the contributing guidelines
I have checked my spelling and grammar with an automated tool
I have previewed my changes to check the markdown renders as I intend
I have run my code to check it works
My changes follow our Style Guide

Who needs to know about this?

@CodeYourFuture/itp-syllabus-team

Start a review

WM5 |ELMIRA ZANGENEH| MODULE-JS3 | PROGRAMMING HUMOUR | WEEK 2 🔗

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

WM5 | Abdihamid Ali | Modul-JS3 | Programmer Humour | week3 🔗

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

I’m getting confused about this “Quality Gate failed” from sonarcloud can anyone explain it to me ? do I have to do anything about it ?
Ask any questions you have for your reviewer.

Start a review

one explanation :

The console.log(“QTY\tITEM\t\t\tTOTAL”); line is used to print the header of the receipt, which includes the titles for each column: “QTY” for quantity, “ITEM” for item name, and “TOTAL” for total cost.

Here’s a breakdown of what each part of the string does:

\t: This is an escape sequence representing a tab character. It adds spacing between the columns.
“QTY”: This is the title for the quantity column.
“ITEM”: This is the title for the item name column.
“\t\t\t”: This adds extra tabs to provide additional spacing between the item name column and the total column.
“TOTAL”: This is the title for the total cost column.

Start a review

In both tasks, destructuring is used when filtering the hogwarts array and when iterating over the filtered results to extract the necessary properties (firstName and lastName) Start a review

See more pull requests

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

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

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.

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.

Start a review

NW6 | nazanin Saedi | TV-project | JS-3 | week3 🔗

This commit introduces new functionality to the website, allowing users to select and view information about multiple TV shows from TVmaze. Start a review

Added a dropdown menu ( 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

four cards per row Start a review

See more pull requests

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.

Learning Objectives

Present a product pitch as a team
Maintain contact with the audience while presenting

Preparation

Have projector and screen available
All group members should have their presentation downloaded on their computers in case the internet or someone’s laptop doesn’t work on the day.
Chose one person to be the timekeeper

Introduction

During the presentations, listen actively to each other and write down questions you would like to ask or feedback you would like to give.

Your teamwork presentation

🎯 Goal: To practice public speaking skills (50 minutes)

Each team will deliver their presentation to the class.

Each team will have 5 minutes to present
After their presentation, each team will have 3 minutes to answer questions from the audience and receive feedback.

If necessary, the cohort can be divided into 2 or 3 groups to ensure all teams have enough time to present and receive feedback.

Learning Objectives

Identify groups of people with similar availability that can work together

Preparation

Open the group spreadsheet and create a new tab called “React.”

Introduction

Interacting with diverse groups fosters empathy, enhancing interpersonal skills for handling others effectively. So focus on grouping with people you might have yet to interact with so much.

Create groups for the next module's group work.

🎯 Goal: Create groups for the next module’s group work. (10 minutes)

These are the tasks that must be completed. Organise yourselves so that not only one person is doing this.

You must consider trainees’ availability.
You must consider how many hours of coursework or prep work has to be done in groups.
You then can define the groups (look for diversity, so people that haven’t
worked together should give it a go, ensure you don’t have gendered groups, etc.)
You can use this link to help you allocate people randomly.
Open the existent spreadsheet for pairs/groups and create a new tab called “React” if this hasn’t been done yet.
Add the groups to the “React” tab
Share the spreadsheet on Slack so it is visible to everyone.

Retro (20 minutes)

A retro is a chance to reflect on this past sprint. You can do this on a Jamboard (make sure someone clicks “Make a copy” before you start, and you work on that together) or on sticky notes on a wall.

Set a timer for 5 minutes.
Write down as many things as you can think of that you’d like to start, stop, and continue doing next sprint.
Write one point per note and keep it short.
When the timer goes off, one person should set a timer for 1 minute and group the notes into themes.
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.
Finally, set a timer for 8 minutes and all discuss the top three themes.