Energiser
Every CYF session begins with an energiser. Usually there’s a rota showing who will lead the energiser. We have some CYF 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.
Resilience 🔗
Learning Objectives
Preparation
Introduction
Resilience is about bouncing back when things don’t go to plan. Life isn’t fair, and you won’t always be successful. Things change. But you can learn to face these challenges.
- You can be proactive in taking action to deal with challenges.
- Look for positive opportunities arising from bad news.
- Stay in touch with people who can help you face challenges.
- Reserve downtime to recover the energy to keep going.
- … and other strategies.
You are here
🎯 Goal: Think positive and find areas where you need to be resilient (20 minutes)
Work in pairs:
- Tell your partner something positive that happened earlier today.
- Tell your partner something that you find challenging in your life.
- Tell your partner about things you do to relax and how much “downtime” you have.
- Describe a changing topic in the world around you that you could either ignore or pro-actively deal with.
- Identify an activity where you are currently stuck at a lower skill level but would need to try doing “a new thing badly” before you could move up a level. Discuss how you could deal with that.
- Identify an activity you were reluctant to do (or do again) because you might fail. What is the worst that could happen?
Resilience scenarios
🎯 Goal: Recognise opportunities in challenges (20 minutes)
Work in pairs. Consider each of the following scenarios. For each, discuss with your partner:
- Feelings you would have from the immediate situation.
- Positive opportunities arise from it.
- What you could do next.
- How your friends could help you deal with this.
Scenarios:
- You have been rejected from a job application when you thought you had an excellent chance.
- Your landlord told you to leave your home and find somewhere else.
- A relative who had been terminally ill for years and needed lots of care has died.
- Your manager thinks you are the only team member who can handle some tasks and assigns too much work to you.
- You are offered two jobs of your dreams, both at a surprisingly good salary.
Lessons Learned
🎯 Goal: Share your tips and speak in public (10 minutes)
- Work as a whole class.
- Share ideas and experiences on how to be resilient. Everybody should speak.
Morning Break
A quick break of fifteen minutes so we can all concentrate on the next piece of work.
Placeholder Workshop 🔗
Workshop Name
Replace this readme with the requirements for your workshop
Learning Objectives
Requirements
Explain the requirements of the workshop. You might want to talk about goals here. You might want to use formal specifications like Given/When/Then. It’s ok for requirements to be in different formats. We want trainees to learn to interpret requirements in many settings and expressions. Just make sure your workshop is active and not a lecture.
Always write your workshop in a readme.md in a folder with the same name as the workshop. This makes it easy to find and easy to show on the curriculum website.
Acceptance Criteria
- I have provided clear success criteria
- These might be related to the objectives and the requirements
- I have given some simple, clear ways for trainees to evaluate their work
- I have run Lighthouse and my Accessibility score is 100
Community Lunch
Every Saturday at CYF 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.
Team Project
Learning Objectives
In this module you are working in a team to build a React app. (You should have created your group already.)
Take this opportunity to work with your team on your React app. You can use this time to work on your app, to discuss your app with your team, ask questions and get help with blockers.
You can use any study group time to work on your product.
🛎️ Code waiting for review 🔗
Below are trainee coursework Pull Requests that need to be reviewed by volunteers.
NW6 | Pedro Eugenio | Eslint and Prop-types section 🔗
Changelist
Added “Eslint and Prop-types” section to the README.md to address issues where Eslint shows red marks below variables due to the demand for prop-types in React projects.
The added section provides clear instructions for resolving this issue by modifying the .eslintrc.cjs file in the project’s root folder. It instructs users to disable the ‘react/prop-types’ rule, thus eliminating the red marks.
Start a reviewWM5 | ADNIYA YOUSAF | FROM SCRATCH | WEEK 3 🔗
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 reviewWM5 | ADNIYA YOUSAF | HIGH-SCORE-TABLES | LEVEL 2 | WEEK2 🔗
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
WM5 | ADNIYA YOUSAF | MODULE REACT | HIGH SCORE | WEEK 1 🔗
- 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
Bump vite from 5.0.10 to 5.0.12 in /high-score-tables 🔗
Bumps vite from 5.0.10 to 5.0.12.
Dependabot will resolve any conflicts with this PR as long as you don’t alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.
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.
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