π§π½βπ€βπ§π½ day-plan
βπ½ 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.
- 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.
π‘ Morning orientation
Learning Objectives
Planning during the week
π£ 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
Teamwork Project S1
π€π½ FeedbackLearning Objectives
Preparation
Introduction
Brainstorm about teamwork in the tech industry.
π― Goal: Discuss teamwork in the tech industry. (35 minutes)
Think about the teams you will work with in tech. Discuss in your team:
- What is your dream job?
- What professional roles will be in your team?
- What other people/teams will you interact with?
- What non-technical skills will you bring?
- What non-technical skills should you develop while at CYF?
- Which of the Belbinβs tole do you identify strongest with?
- Define which team member wο»Ώill be the time keeper for your team.
- Work in your teams for about 10 minutes and write down brief answers to each question.
- Assign one of the team members as speaker to deliver your answers back to the class in maximum 2 minutes.
Discuss the roles in a product team
π― Goal: To discuss the importance of different roles in tech teams. (10 minutes)
The following are the roles typically found within a development team. As you see, there are plenty of roles other than βFull-Stack Developerβ.
Discuss as a class the responsibilities of the following tech roles.
Write a brief description for each of them on a post-it and share the post it on a collaborative board:
- Front-end web developer
- Back-end web developer
- UX/UI designer
- UX researcher
- Product manager
- Quality Assurance/Quality Engineer (tester)
- Tech lead
Team Charter
π― Goal: To discuss the importance of setting clear goals and responsibilities within a team. (15 minutes)
You might come across a ceremony called βteam charterβ in your future work.
Team charters define roles, responsibilities and ways of working. If these are not clear to you when you join a new company, you should ask and seek clarification urgently.
Discuss as a class:
- Why is it important for your team to understand their main goal?
- Why is it important for everybody on your team to understand the role each other plays?
- What is the importance of having clear ways of working?
- What happens when you are not clear about these three points?
Spend the rest of your time clarifying any questions about the project and the coursework for the first week.
π½οΈ 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
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.
Glasgow | May-2025 | Mansoor Munawar | Sprint 2 | Book library π
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Briefly explain your PR. fixed the bugs in book library and refactor code to meet the requirements of the task. And also used “https://github.com/cjyuan/Module-Data-Flows/blob/book-library-feedback/debugging/book-library/feedback.md" to improve my code
Questions
Ask any questions you have for your reviewer.
Start a reviewLondon | 25-ITP-May | Houssam Lahlah | Sprint 3 | Programmer humour π
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Title:
Add Programmer Humour XKCD Comic Project
Description:
This PR adds a small project that fetches and displays the latest XKCD comic using the API https://xkcd.now.sh/?comic=latest.
Features:
- Fetches the latest comic with fetch
- Logs the JSON response to the console
- Dynamically renders the comic image in the DOM
- Includes error handling for failed API requests
- Simple HTML, CSS, and JavaScript setup
- Fully functional and ready for review.
Questions
- Is my approach to fetching and rendering the XKCD comic efficient, and are there ways to improve performance or code structure?
- How can I handle API errors or edge cases more effectively, e.g., if the API is down or returns invalid data?
- Are there best practices for dynamically updating the DOM when adding or replacing images in projects like this?
London | 25-ITP-May | Houssam Lahlah | Sprint 3 | Java script challenges π
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 Region | Cohort | FirstName LastName | Sprint | Assignment Title
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Title: Complete JS and Unit Testing Challenges
Description: This PR merges all completed katas and JS exercises, including:
Factorial, Car Sales, Average, Largest Number, Remove Vowels, Roman Numerals, Password Verifier, String Calculator
Cowsay CLI, Weather App, Dog Photo Gallery
- All Jest tests pass for katas
- Browser projects work with expected functionality
- Modular, tested, and ready for review
Question
- Are there ways to make my test-writing and implementation more efficient?
- Are there any best practices I should follow when structuring my functions and test files?
- How can I improve the readability and maintainability of my code for these katas?
West Midlands| 25-ITP-May | Emin Akturk | Module Data Flows | Book Library π
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 Region | Cohort | FirstName LastName | Sprint | Assignment Title
- 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 reviewWM | ITP-MAY-25 | NAHOM MESFIN | Sprint 2 | Book Library π
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 Region | Cohort | FirstName LastName | Sprint | Assignment Title
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
I debugged and fixed issues preventing books from displaying. and corrected errors when adding a book. then fixed the title/author mix-up, ensured the delete button works, and corrected the read-status logic. I then implemented validation so incomplete book entries show an alert instead of being added to the list.
Start a reviewπ« 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
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
π Retro: Start / Stop / Continue
πΉοΈRetro (20 minutes)
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.
- Set a timer for 5 minutes. There’s one on the RetroTool too.
- 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.