🧑🏾‍🤝‍🧑🏾 day-plan

🔖
  1. Energiser: Word Chain
  2. Morning orientation
  3. Questions and Review Workshop
  4. Morning break
  5. Time Traveller
  6. lunch
  7. Stand Up
  8. Study Group
  9. Code Review
  10. Afternoon break
  11. Study Group
  12. Retro

✍🏽 Register

🔤 Word Chain

Learning Objectives

A fast-paced word association game that works for both in-person and online groups of any size. If you are playing online, write the order of players in the chat to keep track of who is next.

Set a timer for

  1. The first player says any word.
  2. The next player must say a word that begins with the last letter of the previous word. For example: cat → tree → elephant → tower
  3. Continue around the circle or moving clockwise on Zoom gallery.
  4. If a player takes longer than 5 seconds or repeats a word, they’re out.
  5. Last player standing wins.
Variations
  • Restrict words to specific categories (animals, countries, food)
  • Words must be exactly 4 letters long
  • Words must be related to the previous word in meaning

🎡 Morning orientation

Learning Objectives

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:

  1. Assemble the entire group (all volunteers & all trainees) in a circle
  2. 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}”

  3. Ask any newcomers to introduce themselves to the group, and welcome them.
  4. 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.
  5. 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

🔗 Questions and Review Workshop

Question and review workshop

Getting setup 💻

Please follow the steps below:

  1. The whole group should split up into separate breakout rooms. Then each breakout room / table should split up into pairs.

  2. In your pairs, label yourselves person 1 and person 2 - it doesn’t matter who is 1 or 2, you’ll end up swapping. 😄

  3. You will end up swapping roles frequently during this activity. To begin with, Person 1 fork this repository and clone it to your local machine.

  4. Person 2 should clone Person 1’s fork to their local machine.

  5. Once it is cloned, in Github desktop, Person 1 should go to Branch at the top of the window and click New branch… and then enter a name: js-2-week-1-questions. Don’t worry if you don’t understand what branches are - they’ll explained in depth later on in the course.

Answering questions ❓

In this next section, you’ll need to answer some questions ❓

N.B: You may struggle to answer some or all of the questions in this section: however, we’re not trying to trick you or catch you out! It’s important you try answering in your own terms in this section! You’ll really feel the benefit from trying to answer questions that may appear tricky at first.

So for the first question, Person 1 and Person 2 can read the first question.

  • Person 2 try and answer the question out loud in your own words.
  • Person 1 should write down Person 1’s answer in the file and then commit and push your changes.

Then swap over ( so Person 1 now becomes Person 2 and vice versa ) and try the next question.

❗🕥 Don’t spend longer than 3 minutes on each question

You’ll find the first question in js-1-week-2/0.md

Whole group discussion

After you’ve answered questions. The whole group should go through the questions and a volunteer can invite responses from the different pairs. This is a good opportunity to correct, clarify and consolidate our answers collectively.

Review time

After the group discussion, every pair should raise a PR from Person 1’s forked repo to the origin repo. Then ask for feedback by requesting a review of the PR from the pair that is sat to the right of you. Each pair should then review the PR they’ve been requested to review.

🫖 Morning Break

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

⏳ Time traveller

Learning Objectives

Meet the time traveller

In this insight session, you will hear from an alumni who has been through the course and is now working in the tech industry. They will share their experience of training with CYF and how it has helped them in their career.

You will have the opportunity to ask questions and learn from their experience. If you could ask your future self anything about today, what would it be?

Facilitator tipsPut a call out on main Slack for alumni to volunteer to be a time traveller. They should be prepared to share their experience of the course and answer questions from the class.

Please do this a couple of weeks beforehand to give them time to prepare.

🍽️ 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.

🔗 Stand Up

Learning Objectives

Stand-up [30 minutes]🧍‍♂️

Most software development teams have a “stand-up” every day. Even if a team does not follow the agile methodology, stand-ups are used to discuss progress and identify blockers.

What is a stand-up meeting?

  1. Daily
  2. Short
  3. Focused

Traditional stand-up meetings require everyone to stand up so that the meeting is short.

💡Tip

Standup: a focused meeting where all team members share their progress, plans, and problems in a short amount of time.

📝Note

Activity: Prepare your Stand-up (5m)

  1. Set a timer for 5 minutes

  2. Write down three bullet points:

  3. What you worked on yesterday

  4. What issues are blocking you / What problems you encountered

  5. What you will work on today

Set up 🌼

  • Split up into breakout rooms of 5 - 10 people
  • Set a timer for 10 minutes

🧩 Time to Have a First Stand-up

  1. Take turns to describe, in no more than 60 seconds:
    • What you worked on this week.
    • Something that is blocking you or that you struggled with (do not discuss solutions yet).
    • What you plan to work on today. If you need help or want to pair with someone to work on something specific this is a time to communicate that!
  2. After everyone has given an update, reflect on next steps together. Is there something that multiple people said they struggled with that you could team up with? Is someone working on something interesting that you want to know more about?
  3. Where else can you ask a question when you have a problem? e.g. what Slack channels are suitable?

💡Tip

No problem solving in the stand-up!

When someone mentions a problem, it’s not the time to discuss solutions. The goal is to identify blockers and plan the day.

Acceptance Criteria 🧾

After this workshop, every participant:

  • Has participated in a stand-up meeting and can explain what the structure is
  • Has formulated their update in the typical “stand-up” structure
  • Has described at least one technical blocker

🧑🏿‍🔧 Study Group Development

Learning Objectives

This time is set aside for you to work together in small groups to make progress on your coursework and objectives. You should have brought at least one ticket from your backlog to work on and ideally have prepared at least one question to get mentor support on.

You can also choose to do structured activities to consolidate your objectives for this sprint. Your learning journey belongs to you. Think about what you need to do to achieve the objectives for this sprint and how you can use this time to work towards them.

If you are working on a Pull Request, this is a great time to get real time code review from your peers and mentors. Remember to use the GitHub interface to comment on the code and ask questions so your work can be tracked.

🗂️ Options

Optional structured activity: Code Review

🧑🏾‍💻 Mentored code review

Learning Objectives

Our learners get feedback on their work through code review. At work, colleagues review each others code to understand code, look for problems, and both share and learn better ways of doing things.

At CYF every learner should get code review on their work every week.

🕹️Live Code Review

Pair up a volunteer with one or more learners.

  • The volunteer will review a pull request, and talk out loud about what they’re looking for and doing.
  • The learner(s) will ask questions as they do.
Hints and tips
  1. How did you understand what the goal of the PR is? Reading the title and description, looking at the coursework exercises, etc.
  2. The uses of the different tabs in a PR: Conversation, Commits, Files changed.
  3. What made a PR easy or hard to review:
    1. Where unrelated files/lines changed?
    2. Was code consistently formatted? Did indentation help or hurt understanding?
  4. How did you review the code? Did you read top-to-bottom? Did you jump around into and out-of functions? Did you look at tests? Did you clone the code locally and try running it?

🛎️ Code waiting for review 🔗

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

CYF London | Rihanna Poursoltani | Module Structuring and Testing Data | Sprint 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 review
Karla Grajales | Sprint-3 - Module-Structuring-and-Testing-Data | SPRINT 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

In this project, I learned to create simpler, well-structured functions without overcomplicating them. I focused on interpreting instructions carefully to ensure the code behaves as expected. Additionally, I explored how to install Jest, write test cases, and debug them effectively. I also learned to use assertions to validate functionality and handle errors by throwing them instead of returning them, which helped improve the clarity and reliability of the code.

Questions

Ask any questions you have for your reviewer.

Start a review
Karla Grajales | Sprint-2 - Module-Structuring-and-Testing-Data | SPRINT 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

In this project, I learned how to use string methods by referring to the MDN documentation, how to set and manage variables, and how data flows within functions. I also learned how to invoke functions properly, debug issues to understand why something doesn’t work, perform operations on strings, and iterate through strings based on their length.

Questions

Ask any questions you have for your reviewer.

Start a review
Glasgow_Class|Shreef_Ibrahim|Structuring _Testing _Datast|Week2_exercise2_update 🔗

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
WM4 | Fatima Safana | Module-Structuring-and-Testing-Data | WEEK6 🔗

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

🫖 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 Development

Learning Objectives

This time is set aside for you to work together in small groups to make progress on your coursework and objectives. You should have brought at least one ticket from your backlog to work on and ideally have prepared at least one question to get mentor support on.

You can also choose to do structured activities to consolidate your objectives for this sprint. Your learning journey belongs to you. Think about what you need to do to achieve the objectives for this sprint and how you can use this time to work towards them.

If you are working on a Pull Request, this is a great time to get real time code review from your peers and mentors. Remember to use the GitHub interface to comment on the code and ask questions so your work can be tracked.

🗂️ Options

Optional structured activity: Pair Programming

🧑🏿‍🔧🧑🏿‍🔧 Pair programming

Learning Objectives

  • Switch between driver and navigator roles after
  • The “driver” is the person typing on the keyboard, just thinking about what needs to be written
  • The “navigator” reviews what the driver is doing and is thinking about to write next
  • Don’t dominate - this is teamwork

⌛ Time’s up! Take a break! Make a cup of tea. Good job, partners!

Optional structured activity: Predict Explain exercises

🔗 Optional structured activity: Predict Explain exercises

Introductory JS Exercises to do in study group

See dir. Start with 0.md

🔄 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.

  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.