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.
- 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.
Conflict Resolution
🤙🏽 FeedbackLearning Objectives
Introduction
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.
Morning Break
A quick break of fifteen minutes so we can all concentrate on the next piece of work.
🔍 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 JS2 week 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
- Get into pairs or groups of up to three.
- 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.
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.
Study Group
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.
Move test related content to lookup.test.js 🔗
What does this change?
It fixes an inconsistency in the project structure by moving the test case from lookup.js to lookup.test.js, aligning with the established pattern of having tests in separate files.
Common Content?
- Block/s
Common Theme?
- Yes
Issue number: #378
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 reviewAdd 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 reviewNW6 | Sabella Fisseha | JS2 Alarm-Clock App | WEEK 3 🔗
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 reviewNW6 | Rabia Avci | JS2 Module | [TECH ED]Complete week 2 exercises | 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 reviewNW-6 | Zeliha Pala | JS2| [TECH ED] Slideshow| WEEK-4 🔗
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 reviewAfternoon 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.
Study Group
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.
Move test related content to lookup.test.js 🔗
What does this change?
It fixes an inconsistency in the project structure by moving the test case from lookup.js to lookup.test.js, aligning with the established pattern of having tests in separate files.
Common Content?
- Block/s
Common Theme?
- Yes
Issue number: #378
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 reviewAdd 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 reviewNW6 | Sabella Fisseha | JS2 Alarm-Clock App | WEEK 3 🔗
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 reviewNW6 | Rabia Avci | JS2 Module | [TECH ED]Complete week 2 exercises | 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 reviewNW-6 | Zeliha Pala | JS2| [TECH ED] Slideshow| WEEK-4 🔗
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 reviewRetro: Start / Stop / Continue
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.